From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Jan Harkes <jaharkes@cs.cmu.edu>
Subject: [git pull] coda dcache-related cleanups and fixes
Date: Tue, 21 Apr 2026 21:06:36 +0100 [thread overview]
Message-ID: <20260421200636.GE3518998@ZenIV> (raw)
In-Reply-To: <20260407220427.326lgx22n4jgsy6b@cs.cmu.edu>
The following changes since commit 7aaa8047eafd0bd628065b15757d9b48c5f9c07d:
Linux 7.0-rc6 (2026-03-29 15:40:00 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-coda
for you to fetch changes up to e252ed8988578f01da5a4f5aa4c2269f96f03951:
coda_flag_children(): fix a UAF (2026-04-04 21:03:13 -0400)
----------------------------------------------------------------
coda cleanups and fixes
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (3):
coda: is_bad_inode() is always false there
sanitize coda_dentry_delete()
coda_flag_children(): fix a UAF
fs/coda/cache.c | 2 ++
fs/coda/dir.c | 15 +++------------
2 files changed, 5 insertions(+), 12 deletions(-)
next prev parent reply other threads:[~2026-04-21 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-05 2:15 [PATCH 0/3] coda dcache-related cleanups and fixes Al Viro
2026-04-05 2:15 ` [PATCH 1/3] coda: is_bad_inode() is always false there Al Viro
2026-04-05 2:15 ` [PATCH 2/3] sanitize coda_dentry_delete() Al Viro
2026-04-05 2:15 ` [PATCH 3/3] coda_flag_children(): fix a UAF Al Viro
2026-04-07 22:05 ` [PATCH 0/3] coda dcache-related cleanups and fixes Jan Harkes
2026-04-21 20:06 ` Al Viro [this message]
2026-04-21 21:56 ` [git pull] " 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=20260421200636.GE3518998@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jaharkes@cs.cmu.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.