diff options
author | Christian Brauner <brauner@kernel.org> | 2025-08-08 15:52:47 +0200 |
---|---|---|
committer | Christian Brauner <brauner@kernel.org> | 2025-08-11 14:52:41 +0200 |
commit | 573015dfa63c73a653d8bf93930b18d75f9732aa (patch) | |
tree | 1bd1a4e455efd4d7ac7db6e116bb03bdea09de68 /tools/testing/selftests/net/lib/py/utils.py | |
parent | bfa8ee11dc13b63041b90cc16d694f69c4747490 (diff) | |
parent | df579e471111b9f8691d75c980f59cc085fa97a3 (diff) |
Merge patch series "fscontext: do not consume log entries when returning -EMSGSIZE"
Aleksa Sarai <cyphar@cyphar.com> says:
Userspace generally expects APIs that return -EMSGSIZE to allow for them
to adjust their buffer size and retry the operation. However, the
fscontext log would previously clear the message even in the -EMSGSIZE
case.
Given that it is very cheap for us to check whether the buffer is too
small before we remove the message from the ring buffer, let's just do
that instead. While we're at it, refactor some fscontext_read() into a
separate helper to make the ring buffer logic a bit easier to read.
* patches from https://lore.kernel.org/20250807-fscontext-log-cleanups-v3-0-8d91d6242dc3@cyphar.com:
selftests/filesystems: add basic fscontext log tests
fscontext: do not consume log entries when returning -EMSGSIZE
Link: https://lore.kernel.org/20250807-fscontext-log-cleanups-v3-0-8d91d6242dc3@cyphar.com
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions