Commit a10ca095 authored by Linus Torvalds's avatar Linus Torvalds
Browse files

Merge tag 'driver-core-6.3-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core 

Pull driver core fixes from Greg KH:
 "Here are three small changes for 6.3-rc5 semi-related to driver core
  stuff:

   - documentation update where we move the security_bugs file to a more
     relevant location.

   - mdt/spi-nor debugfs memory leak fix that's been floating around for
     a long time and acked by the maintainer

   - cacheinfo bugfix for a regression in 6.3-rc1

  All have been in linux-next with no reported problems"

* tag 'driver-core-6.3-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
  cacheinfo: Fix LLC is not exported through sysfs
  Documentation/security-bugs: move from admin-guide/ to process/
  mtd: spi-nor: fix memory leak when using debugfs_lookup()
parents 95d0b9d8 5c271238

Documentation/admin-guide/index.rst

+0 −1
Original line number Diff line number Diff line
@@ -36,7 +36,6 @@ problems and bugs in particular. 


   reporting-issues

   reporting-regressions

   security-bugs

   bug-hunting

   bug-bisect

   tainted-kernels

Documentation/admin-guide/reporting-issues.rst

+2 −2
Original line number Diff line number Diff line
@@ -395,7 +395,7 @@ might want to be aware of; it for example explains how to add your issue to the 
list of tracked regressions, to ensure it won't fall through the cracks.



What qualifies as security issue is left to your judgment. Consider reading

Documentation/admin-guide/security-bugs.rst before proceeding, as it

Documentation/process/security-bugs.rst before proceeding, as it

provides additional details how to best handle security issues.



An issue is a 'really severe problem' when something totally unacceptably bad
@@ -1269,7 +1269,7 @@ them when sending the report by mail. If you filed it in a bug tracker, forward 
the report's text to these addresses; but on top of it put a small note where

you mention that you filed it with a link to the ticket.



See Documentation/admin-guide/security-bugs.rst for more information.

See Documentation/process/security-bugs.rst for more information.





Duties after the report went out

Documentation/process/howto.rst

+1 −1
Original line number Diff line number Diff line
@@ -138,7 +138,7 @@ required reading: 
    philosophy and is very important for people moving to Linux from

    development on other Operating Systems.



  :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>`

  :ref:`Documentation/process/security-bugs.rst <securitybugs>`

    If you feel you have found a security problem in the Linux kernel,

    please follow the steps in this document to help notify the kernel

    developers, and help solve the issue.

Documentation/process/index.rst

+8 −1
Original line number Diff line number Diff line
@@ -35,6 +35,14 @@ Below are the essential guides that every developer should read. 
   kernel-enforcement-statement

   kernel-driver-statement



For security issues, see:



.. toctree::

   :maxdepth: 1



   security-bugs

   embargoed-hardware-issues



Other guides to the community that are of interest to most developers are:



.. toctree::
@@ -47,7 +55,6 @@ Other guides to the community that are of interest to most developers are: 
   submit-checklist

   kernel-docs

   deprecated

   embargoed-hardware-issues

   maintainers

   researcher-guidelines

Documentation/process/researcher-guidelines.rst

+1 −1
Original line number Diff line number Diff line
@@ -68,7 +68,7 @@ Before contributing, carefully read the appropriate documentation: 
* Documentation/process/development-process.rst

* Documentation/process/submitting-patches.rst

* Documentation/admin-guide/reporting-issues.rst

* Documentation/admin-guide/security-bugs.rst

* Documentation/process/security-bugs.rst



Then send a patch (including a commit log with all the details listed

below) and follow up on any feedback from other developers.