Loading Documentation/ABI/testing/sysfs-fs-f2fs +16 −1 Original line number Diff line number Diff line Loading @@ -121,7 +121,22 @@ What: /sys/fs/f2fs/<disk>/idle_interval Date: January 2016 Contact: "Jaegeuk Kim" <jaegeuk@kernel.org> Description: Controls the idle timing. Controls the idle timing for all paths other than discard and gc path. What: /sys/fs/f2fs/<disk>/discard_idle_interval Date: September 2018 Contact: "Chao Yu" <yuchao0@huawei.com> Contact: "Sahitya Tummala" <stummala@codeaurora.org> Description: Controls the idle timing for discard path. What: /sys/fs/f2fs/<disk>/gc_idle_interval Date: September 2018 Contact: "Chao Yu" <yuchao0@huawei.com> Contact: "Sahitya Tummala" <stummala@codeaurora.org> Description: Controls the idle timing for gc path. What: /sys/fs/f2fs/<disk>/iostat_enable Date: August 2017 Loading Documentation/admin-guide/kernel-parameters.txt +61 −3 Original line number Diff line number Diff line Loading @@ -1070,7 +1070,7 @@ earlyprintk=serial[,0x...[,baudrate]] earlyprintk=ttySn[,baudrate] earlyprintk=dbgp[debugController#] earlyprintk=pciserial,bus:device.function[,baudrate] earlyprintk=pciserial[,force],bus:device.function[,baudrate] earlyprintk=xdbc[xhciController#] earlyprintk is useful when the kernel crashes before Loading Loading @@ -1102,6 +1102,10 @@ The sclp output can only be used on s390. The optional "force" to "pciserial" enables use of a PCI device even when its classcode is not of the UART class. edac_report= [HW,EDAC] Control how to report EDAC event Format: {"on" | "off" | "force"} on: enable EDAC to report H/W event. May be overridden Loading Loading @@ -4172,9 +4176,13 @@ spectre_v2= [X86] Control mitigation of Spectre variant 2 (indirect branch speculation) vulnerability. The default operation protects the kernel from user space attacks. on - unconditionally enable off - unconditionally disable on - unconditionally enable, implies spectre_v2_user=on off - unconditionally disable, implies spectre_v2_user=off auto - kernel detects whether your CPU model is vulnerable Loading @@ -4184,6 +4192,12 @@ CONFIG_RETPOLINE configuration option, and the compiler with which the kernel was built. Selecting 'on' will also enable the mitigation against user space to user space task attacks. Selecting 'off' will disable both the kernel and the user space protections. Specific mitigations can also be selected manually: retpoline - replace indirect branches Loading @@ -4193,6 +4207,48 @@ Not specifying this option is equivalent to spectre_v2=auto. spectre_v2_user= [X86] Control mitigation of Spectre variant 2 (indirect branch speculation) vulnerability between user space tasks on - Unconditionally enable mitigations. Is enforced by spectre_v2=on off - Unconditionally disable mitigations. Is enforced by spectre_v2=off prctl - Indirect branch speculation is enabled, but mitigation can be enabled via prctl per thread. The mitigation control state is inherited on fork. prctl,ibpb - Like "prctl" above, but only STIBP is controlled per thread. IBPB is issued always when switching between different user space processes. seccomp - Same as "prctl" above, but all seccomp threads will enable the mitigation unless they explicitly opt out. seccomp,ibpb - Like "seccomp" above, but only STIBP is controlled per thread. IBPB is issued always when switching between different user space processes. auto - Kernel selects the mitigation depending on the available CPU features and vulnerability. Default mitigation: If CONFIG_SECCOMP=y then "seccomp", otherwise "prctl" Not specifying this option is equivalent to spectre_v2_user=auto. spec_store_bypass_disable= [HW] Control Speculative Store Bypass (SSB) Disable mitigation (Speculative Store Bypass vulnerability) Loading Loading @@ -4690,6 +4746,8 @@ prevent spurious wakeup); n = USB_QUIRK_DELAY_CTRL_MSG (Device needs a pause after every control message); o = USB_QUIRK_HUB_SLOW_RESET (Hub needs extra delay after resetting its port); Example: quirks=0781:5580:bk,0a5c:5834:gij usbhid.mousepoll= Loading Documentation/admin-guide/security-bugs.rst +30 −18 Original line number Diff line number Diff line Loading @@ -26,23 +26,35 @@ information is helpful. Any exploit code is very helpful and will not be released without consent from the reporter unless it has already been made public. Disclosure ---------- The goal of the Linux kernel security team is to work with the bug submitter to understand and fix the bug. We prefer to publish the fix as soon as possible, but try to avoid public discussion of the bug itself and leave that to others. Publishing the fix may be delayed when the bug or the fix is not yet fully understood, the solution is not well-tested or for vendor coordination. However, we expect these delays to be short, measurable in days, not weeks or months. A release date is negotiated by the security team working with the bug submitter as well as vendors. However, the kernel security team holds the final say when setting a timeframe. The timeframe varies from immediate (esp. if it's already publicly known bug) to a few weeks. As a basic default policy, we expect report date to release date to be on the order of 7 days. Disclosure and embargoed information ------------------------------------ The security list is not a disclosure channel. For that, see Coordination below. Once a robust fix has been developed, the release process starts. Fixes for publicly known bugs are released immediately. Although our preference is to release fixes for publicly undisclosed bugs as soon as they become available, this may be postponed at the request of the reporter or an affected party for up to 7 calendar days from the start of the release process, with an exceptional extension to 14 calendar days if it is agreed that the criticality of the bug requires more time. The only valid reason for deferring the publication of a fix is to accommodate the logistics of QA and large scale rollouts which require release coordination. Whilst embargoed information may be shared with trusted individuals in order to develop a fix, such information will not be published alongside the fix or on any other disclosure channel without the permission of the reporter. This includes but is not limited to the original bug report and followup discussions (if any), exploits, CVE information or the identity of the reporter. In other words our only interest is in getting bugs fixed. All other information submitted to the security list and any followup discussions of the report are treated confidentially even after the embargo has been lifted, in perpetuity. Coordination ------------ Loading @@ -68,7 +80,7 @@ may delay the bug handling. If a reporter wishes to have a CVE identifier assigned ahead of public disclosure, they will need to contact the private linux-distros list, described above. When such a CVE identifier is known before a patch is provided, it is desirable to mention it in the commit message, though. message if the reporter agrees. Non-disclosure agreements ------------------------- Loading Documentation/devicetree/bindings/net/can/holt_hi311x.txt +1 −1 Original line number Diff line number Diff line Loading @@ -17,7 +17,7 @@ Example: reg = <1>; clocks = <&clk32m>; interrupt-parent = <&gpio4>; interrupts = <13 IRQ_TYPE_EDGE_RISING>; interrupts = <13 IRQ_TYPE_LEVEL_HIGH>; vdd-supply = <®5v0>; xceiver-supply = <®5v0>; }; Documentation/filesystems/f2fs.txt +7 −1 Original line number Diff line number Diff line Loading @@ -172,9 +172,10 @@ fault_type=%d Support configuring fault injection type, should be FAULT_DIR_DEPTH 0x000000100 FAULT_EVICT_INODE 0x000000200 FAULT_TRUNCATE 0x000000400 FAULT_IO 0x000000800 FAULT_READ_IO 0x000000800 FAULT_CHECKPOINT 0x000001000 FAULT_DISCARD 0x000002000 FAULT_WRITE_IO 0x000004000 mode=%s Control block allocation mode which supports "adaptive" and "lfs". In "lfs" mode, there should be no random writes towards main area. Loading Loading @@ -211,6 +212,11 @@ fsync_mode=%s Control the policy of fsync. Currently supports "posix", non-atomic files likewise "nobarrier" mount option. test_dummy_encryption Enable dummy encryption, which provides a fake fscrypt context. The fake fscrypt context is used by xfstests. checkpoint=%s Set to "disable" to turn off checkpointing. Set to "enable" to reenable checkpointing. Is enabled by default. While disabled, any unmounting or unexpected shutdowns will cause the filesystem contents to appear as they did when the filesystem was mounted with that option. ================================================================================ DEBUGFS ENTRIES Loading Loading
Documentation/ABI/testing/sysfs-fs-f2fs +16 −1 Original line number Diff line number Diff line Loading @@ -121,7 +121,22 @@ What: /sys/fs/f2fs/<disk>/idle_interval Date: January 2016 Contact: "Jaegeuk Kim" <jaegeuk@kernel.org> Description: Controls the idle timing. Controls the idle timing for all paths other than discard and gc path. What: /sys/fs/f2fs/<disk>/discard_idle_interval Date: September 2018 Contact: "Chao Yu" <yuchao0@huawei.com> Contact: "Sahitya Tummala" <stummala@codeaurora.org> Description: Controls the idle timing for discard path. What: /sys/fs/f2fs/<disk>/gc_idle_interval Date: September 2018 Contact: "Chao Yu" <yuchao0@huawei.com> Contact: "Sahitya Tummala" <stummala@codeaurora.org> Description: Controls the idle timing for gc path. What: /sys/fs/f2fs/<disk>/iostat_enable Date: August 2017 Loading
Documentation/admin-guide/kernel-parameters.txt +61 −3 Original line number Diff line number Diff line Loading @@ -1070,7 +1070,7 @@ earlyprintk=serial[,0x...[,baudrate]] earlyprintk=ttySn[,baudrate] earlyprintk=dbgp[debugController#] earlyprintk=pciserial,bus:device.function[,baudrate] earlyprintk=pciserial[,force],bus:device.function[,baudrate] earlyprintk=xdbc[xhciController#] earlyprintk is useful when the kernel crashes before Loading Loading @@ -1102,6 +1102,10 @@ The sclp output can only be used on s390. The optional "force" to "pciserial" enables use of a PCI device even when its classcode is not of the UART class. edac_report= [HW,EDAC] Control how to report EDAC event Format: {"on" | "off" | "force"} on: enable EDAC to report H/W event. May be overridden Loading Loading @@ -4172,9 +4176,13 @@ spectre_v2= [X86] Control mitigation of Spectre variant 2 (indirect branch speculation) vulnerability. The default operation protects the kernel from user space attacks. on - unconditionally enable off - unconditionally disable on - unconditionally enable, implies spectre_v2_user=on off - unconditionally disable, implies spectre_v2_user=off auto - kernel detects whether your CPU model is vulnerable Loading @@ -4184,6 +4192,12 @@ CONFIG_RETPOLINE configuration option, and the compiler with which the kernel was built. Selecting 'on' will also enable the mitigation against user space to user space task attacks. Selecting 'off' will disable both the kernel and the user space protections. Specific mitigations can also be selected manually: retpoline - replace indirect branches Loading @@ -4193,6 +4207,48 @@ Not specifying this option is equivalent to spectre_v2=auto. spectre_v2_user= [X86] Control mitigation of Spectre variant 2 (indirect branch speculation) vulnerability between user space tasks on - Unconditionally enable mitigations. Is enforced by spectre_v2=on off - Unconditionally disable mitigations. Is enforced by spectre_v2=off prctl - Indirect branch speculation is enabled, but mitigation can be enabled via prctl per thread. The mitigation control state is inherited on fork. prctl,ibpb - Like "prctl" above, but only STIBP is controlled per thread. IBPB is issued always when switching between different user space processes. seccomp - Same as "prctl" above, but all seccomp threads will enable the mitigation unless they explicitly opt out. seccomp,ibpb - Like "seccomp" above, but only STIBP is controlled per thread. IBPB is issued always when switching between different user space processes. auto - Kernel selects the mitigation depending on the available CPU features and vulnerability. Default mitigation: If CONFIG_SECCOMP=y then "seccomp", otherwise "prctl" Not specifying this option is equivalent to spectre_v2_user=auto. spec_store_bypass_disable= [HW] Control Speculative Store Bypass (SSB) Disable mitigation (Speculative Store Bypass vulnerability) Loading Loading @@ -4690,6 +4746,8 @@ prevent spurious wakeup); n = USB_QUIRK_DELAY_CTRL_MSG (Device needs a pause after every control message); o = USB_QUIRK_HUB_SLOW_RESET (Hub needs extra delay after resetting its port); Example: quirks=0781:5580:bk,0a5c:5834:gij usbhid.mousepoll= Loading
Documentation/admin-guide/security-bugs.rst +30 −18 Original line number Diff line number Diff line Loading @@ -26,23 +26,35 @@ information is helpful. Any exploit code is very helpful and will not be released without consent from the reporter unless it has already been made public. Disclosure ---------- The goal of the Linux kernel security team is to work with the bug submitter to understand and fix the bug. We prefer to publish the fix as soon as possible, but try to avoid public discussion of the bug itself and leave that to others. Publishing the fix may be delayed when the bug or the fix is not yet fully understood, the solution is not well-tested or for vendor coordination. However, we expect these delays to be short, measurable in days, not weeks or months. A release date is negotiated by the security team working with the bug submitter as well as vendors. However, the kernel security team holds the final say when setting a timeframe. The timeframe varies from immediate (esp. if it's already publicly known bug) to a few weeks. As a basic default policy, we expect report date to release date to be on the order of 7 days. Disclosure and embargoed information ------------------------------------ The security list is not a disclosure channel. For that, see Coordination below. Once a robust fix has been developed, the release process starts. Fixes for publicly known bugs are released immediately. Although our preference is to release fixes for publicly undisclosed bugs as soon as they become available, this may be postponed at the request of the reporter or an affected party for up to 7 calendar days from the start of the release process, with an exceptional extension to 14 calendar days if it is agreed that the criticality of the bug requires more time. The only valid reason for deferring the publication of a fix is to accommodate the logistics of QA and large scale rollouts which require release coordination. Whilst embargoed information may be shared with trusted individuals in order to develop a fix, such information will not be published alongside the fix or on any other disclosure channel without the permission of the reporter. This includes but is not limited to the original bug report and followup discussions (if any), exploits, CVE information or the identity of the reporter. In other words our only interest is in getting bugs fixed. All other information submitted to the security list and any followup discussions of the report are treated confidentially even after the embargo has been lifted, in perpetuity. Coordination ------------ Loading @@ -68,7 +80,7 @@ may delay the bug handling. If a reporter wishes to have a CVE identifier assigned ahead of public disclosure, they will need to contact the private linux-distros list, described above. When such a CVE identifier is known before a patch is provided, it is desirable to mention it in the commit message, though. message if the reporter agrees. Non-disclosure agreements ------------------------- Loading
Documentation/devicetree/bindings/net/can/holt_hi311x.txt +1 −1 Original line number Diff line number Diff line Loading @@ -17,7 +17,7 @@ Example: reg = <1>; clocks = <&clk32m>; interrupt-parent = <&gpio4>; interrupts = <13 IRQ_TYPE_EDGE_RISING>; interrupts = <13 IRQ_TYPE_LEVEL_HIGH>; vdd-supply = <®5v0>; xceiver-supply = <®5v0>; };
Documentation/filesystems/f2fs.txt +7 −1 Original line number Diff line number Diff line Loading @@ -172,9 +172,10 @@ fault_type=%d Support configuring fault injection type, should be FAULT_DIR_DEPTH 0x000000100 FAULT_EVICT_INODE 0x000000200 FAULT_TRUNCATE 0x000000400 FAULT_IO 0x000000800 FAULT_READ_IO 0x000000800 FAULT_CHECKPOINT 0x000001000 FAULT_DISCARD 0x000002000 FAULT_WRITE_IO 0x000004000 mode=%s Control block allocation mode which supports "adaptive" and "lfs". In "lfs" mode, there should be no random writes towards main area. Loading Loading @@ -211,6 +212,11 @@ fsync_mode=%s Control the policy of fsync. Currently supports "posix", non-atomic files likewise "nobarrier" mount option. test_dummy_encryption Enable dummy encryption, which provides a fake fscrypt context. The fake fscrypt context is used by xfstests. checkpoint=%s Set to "disable" to turn off checkpointing. Set to "enable" to reenable checkpointing. Is enabled by default. While disabled, any unmounting or unexpected shutdowns will cause the filesystem contents to appear as they did when the filesystem was mounted with that option. ================================================================================ DEBUGFS ENTRIES Loading
