From: Greg KH <gregkh@linuxfoundation.org>
To: Kyle Zeng <zengyhkyle@gmail.com>
Cc: jlbec@evilplan.org, hch@lst.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] configfs: fix a race in configfs_lookup() in stable-5.10.y
Date: Sat, 2 Sep 2023 08:45:31 +0200 [thread overview]
Message-ID: <2023090222-rover-gilled-22d2@gregkh> (raw)
In-Reply-To: <ZPKG3VxTIcATSLCX@westworld>
On Fri, Sep 01, 2023 at 05:50:37PM -0700, Kyle Zeng wrote:
> Basically porting c42dd069be8dfc9b2239a5c89e73bbd08ab35de0 to
> stable-v5.10.y to avoid race condition between configfs_dir_lseek and
> configfs_lookup since they both operate ->s_childre and configfs_lookup
> forgets to obtain the lock.
>
> Signed-off-by: Kyle Zeng <zengyhkyle@gmail.com>
> ---
> fs/configfs/dir.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/configfs/dir.c b/fs/configfs/dir.c
> index 12388ed4faa5..0b7e9ab517d5 100644
> --- a/fs/configfs/dir.c
> +++ b/fs/configfs/dir.c
> @@ -479,6 +479,7 @@ static struct dentry * configfs_lookup(struct inode *dir,
> if (!configfs_dirent_is_ready(parent_sd))
> goto out;
>
> + spin_lock(&configfs_dirent_lock);
> list_for_each_entry(sd, &parent_sd->s_children, s_sibling) {
> if (sd->s_type & CONFIGFS_NOT_PINNED) {
> const unsigned char * name = configfs_get_name(sd);
> @@ -491,6 +492,7 @@ static struct dentry * configfs_lookup(struct inode *dir,
> break;
> }
> }
> + spin_unlock(&configfs_dirent_lock);
>
> if (!found) {
> /*
> --
> 2.34.1
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
prev parent reply other threads:[~2023-09-02 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 0:50 Kyle Zeng
2023-09-02 6:45 ` Greg KH [this message]
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=2023090222-rover-gilled-22d2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zengyhkyle@gmail.com \
/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
all inboxes | Powered by JetHome®