diff options
| author | Corey Minyard <corey@minyard.net> | 2026-04-20 12:39:51 -0500 |
|---|---|---|
| committer | Corey Minyard <corey@minyard.net> | 2026-04-28 12:59:08 -0500 |
| commit | c4cca236968683eb0d59abfb12d5c7e4d8514227 (patch) | |
| tree | 2c1515d4e55f2d15be84f397d816a484a5b431d1 /include/linux/stackprotector.h | |
| parent | 36920f30e78e69df01f9691c470b6f3ba8aebf98 (diff) | |
ipmi: Add limits to event and receive message requests
The driver would just fetch events and receive messages until the
BMC said it was done. To avoid issues with BMCs that never say they are
done, add a limit of 10 fetches at a time.
In addition, an si interface has an attn state it can return from the
hardware which is supposed to cause a flag fetch to see if the driver
needs to fetch events or message or a few other things. If the attn
bit gets stuck, it's a similar problem. So allow messages in between
flag fetches so the driver itself doesn't get stuck.
This is a more general fix than the previous fix for the specific bad
BMC, but should fix the more general issue of a BMC that won't stop
saying it has data.
This has been there from the beginning of the driver. It's not a bug
per-se, but it is accounting for bugs in BMCs.
Reported-by: Matt Fleming <mfleming@cloudflare.com>
Closes: https://lore.kernel.org/lkml/20260415115930.3428942-1-matt@readmodwrite.com/
Fixes: <1da177e4c3f4> ("Linux-2.6.12-rc2")
Cc: stable@vger.kernel.org
Signed-off-by: Corey Minyard <corey@minyard.net>
Diffstat (limited to 'include/linux/stackprotector.h')
0 files changed, 0 insertions, 0 deletions
