[PATCH RFC 05/16] proc: let procfs own the seq_file of proc_create_seq() and friends
sashiko-bot at kernel.org
sashiko-bot at kernel.org
Tue Nov 3 07:01:09 PST 2026
> proc_create_seq_private(), proc_create_single_data() and their network
> namespace variants keep the seq_operations or the show function in the
> entry already. Let procfs own the seq_file for all of them. For the
> network namespace variants ->proc_open() and ->proc_release() keep
> taking and dropping the reference to the network namespace.
>
> That's most of /proc/net, among them the files of xt_hashlimit and
> /proc/net/dev_snmp6/<dev>. A reader that faults on its buffer no longer
> holds up their removal.
>
> Reported-by: Chris Mason <mason at kernel.org>
> Fixes: 786d7e1612f0 ("Fix rmmod/read/write races in /proc entries")
> Signed-off-by: Christian Brauner (Amutable) <brauner at kernel.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261102-work-procfs-core-v1-0-75df35e4f8b8@kernel.org?part=5
More information about the kexec
mailing list