[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250703120244.96908-1-laurabrehm@hey.com>
Date: Thu, 3 Jul 2025 14:02:42 +0200
From: Laura Brehm <laurajfbrehm@...il.com>
To: linux-kernel@...r.kernel.org
Cc: Laura Brehm <laurabrehm@....com>
Subject: [PATCH 0/2] coredump: socket PIDFD+PIDFD_INFO_COREDUMP issues
Preamble: This is my first foray into the kernel mailing list, so
apologies for any blunders - I've tried my best to make sure
this is addressed to the right place, and to follow the
appropriate conventions, but I'm likely to miss many.
This set of patches addresses some issues I *think* I've identified with
some of the new coredump socket/PIDFD_INFO_COREDUMP ioctl functionality.
There's a reasonable chance that these aren't actual issues - I've
tried my best to make sure the error wasn't on my end using these
features, and checked the kernel tests for them to make sure I'm not
doing anything wrong, but it's definitely still possible since I don't
have a lot of experience with the kernel.
I sent these as a PATCH because it seemed the most straightforward way
to illustrate the issues I'm mentioning.
They're signed off, so if these do turn out to be actual issues which
the included patches address/can address with some changes, I'd like
to see them merged.
However,in the likely case the issues I brought up are not real/I'm
just doing something wrong, please accept my apologies for the spam.
Laura Brehm (2):
coredump: fix race condition between connect and putting pidfs dentry
coredump: fix PIDFD_INFO_COREDUMP ioctl check
fs/coredump.c | 8 ++------
fs/pidfs.c | 2 +-
2 files changed, 3 insertions(+), 7 deletions(-)
base-commit: 66701750d5565c574af42bef0b789ce0203e3071
--
2.39.5 (Apple Git-154)
Powered by blists - more mailing lists