/openbmc/entity-manager/configurations/ |
H A D | sbp1_chassis.json | dab17c1a Fri Oct 13 10:33:12 CDT 2023 Patrick Rudolph <patrick.rudolph@9elements.com> configurations: sbp1: Set failsafe to 35%
Set a failsafe of 35% that will keep all mainboard components cool enough to prevent a thermal initiated emergency shutdown.
This value will also be used when the BMC is restarting or when the phosphor-pid-control has been stopped.
Change-Id: I86f53a5e890840f9d5f3a62e90a1a3bc43c4374a Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
/openbmc/linux/include/trace/events/ |
H A D | afs.h | dab17c1a Thu Nov 02 10:27:52 CDT 2017 David Howells <dhowells@redhat.com> afs: Fix directory read/modify race
Because parsing of the directory wasn't being done under any sort of lock, the pages holding the directory content can get invalidated whilst the parsing is ongoing.
Further, the directory page check function gets called outside of the page lock, so if the page gets cleared or updated, this may return reports of bad magic numbers in the directory page.
Also, the directory may change size whilst checking and parsing are ongoing, so more care needs to be taken here.
Fix this by:
(1) Perform the page check from the page filling function before we set PageUptodate and drop the page lock.
(2) Check for the file having shrunk and the page having been abandoned before checking the page contents.
(3) Lock the page whilst parsing it for the directory iterator.
Whilst we're at it, add a tracepoint to report check failure.
Signed-off-by: David Howells <dhowells@redhat.com> dab17c1a Thu Nov 02 10:27:52 CDT 2017 David Howells <dhowells@redhat.com> afs: Fix directory read/modify race Because parsing of the directory wasn't being done under any sort of lock, the pages holding the directory content can get invalidated whilst the parsing is ongoing. Further, the directory page check function gets called outside of the page lock, so if the page gets cleared or updated, this may return reports of bad magic numbers in the directory page. Also, the directory may change size whilst checking and parsing are ongoing, so more care needs to be taken here. Fix this by: (1) Perform the page check from the page filling function before we set PageUptodate and drop the page lock. (2) Check for the file having shrunk and the page having been abandoned before checking the page contents. (3) Lock the page whilst parsing it for the directory iterator. Whilst we're at it, add a tracepoint to report check failure. Signed-off-by: David Howells <dhowells@redhat.com>
|
/openbmc/linux/fs/afs/ |
H A D | file.c | dab17c1a Thu Nov 02 10:27:52 CDT 2017 David Howells <dhowells@redhat.com> afs: Fix directory read/modify race
Because parsing of the directory wasn't being done under any sort of lock, the pages holding the directory content can get invalidated whilst the parsing is ongoing.
Further, the directory page check function gets called outside of the page lock, so if the page gets cleared or updated, this may return reports of bad magic numbers in the directory page.
Also, the directory may change size whilst checking and parsing are ongoing, so more care needs to be taken here.
Fix this by:
(1) Perform the page check from the page filling function before we set PageUptodate and drop the page lock.
(2) Check for the file having shrunk and the page having been abandoned before checking the page contents.
(3) Lock the page whilst parsing it for the directory iterator.
Whilst we're at it, add a tracepoint to report check failure.
Signed-off-by: David Howells <dhowells@redhat.com> dab17c1a Thu Nov 02 10:27:52 CDT 2017 David Howells <dhowells@redhat.com> afs: Fix directory read/modify race Because parsing of the directory wasn't being done under any sort of lock, the pages holding the directory content can get invalidated whilst the parsing is ongoing. Further, the directory page check function gets called outside of the page lock, so if the page gets cleared or updated, this may return reports of bad magic numbers in the directory page. Also, the directory may change size whilst checking and parsing are ongoing, so more care needs to be taken here. Fix this by: (1) Perform the page check from the page filling function before we set PageUptodate and drop the page lock. (2) Check for the file having shrunk and the page having been abandoned before checking the page contents. (3) Lock the page whilst parsing it for the directory iterator. Whilst we're at it, add a tracepoint to report check failure. Signed-off-by: David Howells <dhowells@redhat.com>
|
H A D | dir.c | dab17c1a Thu Nov 02 10:27:52 CDT 2017 David Howells <dhowells@redhat.com> afs: Fix directory read/modify race
Because parsing of the directory wasn't being done under any sort of lock, the pages holding the directory content can get invalidated whilst the parsing is ongoing.
Further, the directory page check function gets called outside of the page lock, so if the page gets cleared or updated, this may return reports of bad magic numbers in the directory page.
Also, the directory may change size whilst checking and parsing are ongoing, so more care needs to be taken here.
Fix this by:
(1) Perform the page check from the page filling function before we set PageUptodate and drop the page lock.
(2) Check for the file having shrunk and the page having been abandoned before checking the page contents.
(3) Lock the page whilst parsing it for the directory iterator.
Whilst we're at it, add a tracepoint to report check failure.
Signed-off-by: David Howells <dhowells@redhat.com> dab17c1a Thu Nov 02 10:27:52 CDT 2017 David Howells <dhowells@redhat.com> afs: Fix directory read/modify race Because parsing of the directory wasn't being done under any sort of lock, the pages holding the directory content can get invalidated whilst the parsing is ongoing. Further, the directory page check function gets called outside of the page lock, so if the page gets cleared or updated, this may return reports of bad magic numbers in the directory page. Also, the directory may change size whilst checking and parsing are ongoing, so more care needs to be taken here. Fix this by: (1) Perform the page check from the page filling function before we set PageUptodate and drop the page lock. (2) Check for the file having shrunk and the page having been abandoned before checking the page contents. (3) Lock the page whilst parsing it for the directory iterator. Whilst we're at it, add a tracepoint to report check failure. Signed-off-by: David Howells <dhowells@redhat.com>
|
H A D | internal.h | dab17c1a Thu Nov 02 10:27:52 CDT 2017 David Howells <dhowells@redhat.com> afs: Fix directory read/modify race
Because parsing of the directory wasn't being done under any sort of lock, the pages holding the directory content can get invalidated whilst the parsing is ongoing.
Further, the directory page check function gets called outside of the page lock, so if the page gets cleared or updated, this may return reports of bad magic numbers in the directory page.
Also, the directory may change size whilst checking and parsing are ongoing, so more care needs to be taken here.
Fix this by:
(1) Perform the page check from the page filling function before we set PageUptodate and drop the page lock.
(2) Check for the file having shrunk and the page having been abandoned before checking the page contents.
(3) Lock the page whilst parsing it for the directory iterator.
Whilst we're at it, add a tracepoint to report check failure.
Signed-off-by: David Howells <dhowells@redhat.com> dab17c1a Thu Nov 02 10:27:52 CDT 2017 David Howells <dhowells@redhat.com> afs: Fix directory read/modify race Because parsing of the directory wasn't being done under any sort of lock, the pages holding the directory content can get invalidated whilst the parsing is ongoing. Further, the directory page check function gets called outside of the page lock, so if the page gets cleared or updated, this may return reports of bad magic numbers in the directory page. Also, the directory may change size whilst checking and parsing are ongoing, so more care needs to be taken here. Fix this by: (1) Perform the page check from the page filling function before we set PageUptodate and drop the page lock. (2) Check for the file having shrunk and the page having been abandoned before checking the page contents. (3) Lock the page whilst parsing it for the directory iterator. Whilst we're at it, add a tracepoint to report check failure. Signed-off-by: David Howells <dhowells@redhat.com>
|