[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251128-pirat-miteinander-cdfad90de5f4@brauner>
Date: Fri, 28 Nov 2025 10:39:54 +0100
From: Christian Brauner <brauner@...nel.org>
To: syzbot <syzbot+bfc9a0ccf0de47d04e8c@...kaller.appspotmail.com>,
NeilBrown <neilb@...mail.net>
Cc: Christian Brauner <brauner@...nel.org>,
amir73il@...il.com,
linux-kernel@...r.kernel.org,
linux-unionfs@...r.kernel.org,
miklos@...redi.hu,
syzkaller-bugs@...glegroups.com
Subject: Re: [PATCH] ovl: fail ovl_lock_rename_workdir() if either target is unhashed
On Fri, 28 Nov 2025 12:22:35 +1100, NeilBrown wrote:
> As well as checking that the parent hasn't changed after getting the
> lock we need to check that the dentry hasn't been unhashed.
> Otherwise we might try to rename something that has been removed.
>
>
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/1] ovl: fail ovl_lock_rename_workdir() if either target is unhashed
https://git.kernel.org/vfs/vfs/c/4ef470912f91
Powered by blists - more mailing lists