From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>, Kyle Zeng <zengyhkyle@gmail.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org
Subject: Re: [PATCH 5.10 000/406] 5.10.195-rc1 review
Date: Wed, 20 Sep 2023 10:11:06 +0200 [thread overview]
Message-ID: <2023092009-angriness-sank-ae4f@gregkh> (raw)
In-Reply-To: <07a04540-554c-4394-1e79-46ea665f8c03@roeck-us.net>
On Tue, Sep 19, 2023 at 09:57:25PM -0700, Guenter Roeck wrote:
> On 9/17/23 12:07, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.195 release.
> > There are 406 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Tue, 19 Sep 2023 19:10:04 +0000.
> > Anything received after that time might be too late.
> >
>
> chromeos-5.10 locks up in configfs_lookup() after the merge of v5.10.195.
>
> I am a bit puzzled because I see
>
> c709c7ca020a configfs: fix a race in configfs_lookup()
>
> in v5.10.195 but not in the list of commits below. I guess I must be
> missing something.
It was part of the big patchset, it was posted here:
https://lore.kernel.org/r/20230917191101.511939651@linuxfoundation.org
Not hidden at all :)
and was submitted here:
https://lore.kernel.org/r/ZPOZFHHA0abVmGx+@westworld
> Either case, the code now looks as follows.
>
> configfs_lookup()
> {
> ...
> spin_lock(&configfs_dirent_lock);
> ...
> err = configfs_attach_attr(sd, dentry);
> ...
> spin_unlock(&configfs_dirent_lock);
> ...
> }
>
> and
>
> configfs_attach_attr(...)
> {
> ...
> spin_lock(&configfs_dirent_lock);
> ...
> }
>
> which unless it is way too late here and I really need to go to sleep
> just won't work.
Kyle, you did the backport, any comments?
thanks,
greg k-h
next prev parent reply other threads:[~2023-09-20 8:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 19:07 [PATCH 5.10 000/406] 5.10.195-rc1 review Greg Kroah-Hartman
2023-09-17 19:08 ` [PATCH 5.10 067/406] eventfd: prevent underflow for eventfd semaphores Greg Kroah-Hartman
2023-09-18 7:57 ` [PATCH 5.10 000/406] 5.10.195-rc1 review Pavel Machek
2023-09-18 12:46 ` Jon Hunter
2023-09-18 17:46 ` Florian Fainelli
2023-09-18 18:33 ` Guenter Roeck
2023-09-18 22:25 ` Shuah Khan
2023-09-18 22:27 ` Shuah Khan
2023-09-19 8:03 ` Naresh Kamboju
2023-09-20 4:57 ` Guenter Roeck
2023-09-20 8:11 ` Greg Kroah-Hartman [this message]
2023-09-20 15:18 ` Guenter Roeck
2023-09-20 17:01 ` Florian Fainelli
2023-09-20 19:13 ` Kyle Zeng
2023-09-21 7:13 ` Greg Kroah-Hartman
2023-09-21 20:35 ` Joel Fernandes
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=2023092009-angriness-sank-ae4f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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