From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [git pull] proc_sys_compare() fix
Date: Sun, 6 Jul 2025 20:06:49 +0100 [thread overview]
Message-ID: <20250706190649.GC1880847@ZenIV> (raw)
The following changes since commit d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af:
Linux 6.16-rc4 (2025-06-29 13:09:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes
for you to fetch changes up to b969f9614885c20f903e1d1f9445611daf161d6d:
fix proc_sys_compare() handling of in-lookup dentries (2025-07-03 20:59:09 -0400)
----------------------------------------------------------------
fix for the breakage spotted by Neil in the interplay between /proc/sys
->d_compare() weirdness and parallel lookups
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (1):
fix proc_sys_compare() handling of in-lookup dentries
fs/proc/inode.c | 2 +-
fs/proc/proc_sysctl.c | 18 +++++++++++-------
2 files changed, 12 insertions(+), 8 deletions(-)
next reply other threads:[~2025-07-06 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 19:06 Al Viro [this message]
2025-07-06 21:09 ` [git pull] proc_sys_compare() fix pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250706190649.GC1880847@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox