From: Nhat Pham <nphamcs@gmail.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm <linux-mm@kvack.org>,
syzbot <syzbot+3c6cac1550288f8e7060@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] workingset: add missing rcu_read_unlock() in lru_gen_refault()
Date: Tue, 9 May 2023 16:59:24 -0700 [thread overview]
Message-ID: <CAKEwX=NsutS53FaSBAo12FQ+dTtpVBr2TR6mJN-bEKFZa4w4jQ@mail.gmail.com> (raw)
In-Reply-To: <610781bc-cf11-fc89-a46f-87cb8235d439@I-love.SAKURA.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
On Tue, May 9, 2023 at 3:23 PM Tetsuo Handa <
penguin-kernel@i-love.sakura.ne.jp> wrote:
> syzbot is reporting sleep in RCU context, for commit d66c718d28ac
> ("workingset: refactor LRU refault to expose refault recency check")
> missed rcu_read_unlock().
>
> Reported-by: syzbot <syzbot+3c6cac1550288f8e7060@syzkaller.appspotmail.com
> >
> Closes: https://syzkaller.appspot.com/bug?extid=3c6cac1550288f8e7060
> Signed-off-by
> <https://syzkaller.appspot.com/bug?extid=3c6cac1550288f8e7060Signed-off-by>:
> Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Fixes: d66c718d28ac ("workingset: refactor LRU refault to expose refault
> recency check")
> ---
> mm/workingset.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/workingset.c b/mm/workingset.c
> index d81f9dafc9f1..90ae785d4c9c 100644
> --- a/mm/workingset.c
> +++ b/mm/workingset.c
> @@ -303,7 +303,7 @@ static void lru_gen_refault(struct folio *folio, void
> *shadow)
> goto unlock;
>
> if (pgdat != folio_pgdat(folio))
> - return;
> + goto unlock;
>
> lruvec = mem_cgroup_lruvec(memcg, pgdat);
> lrugen = &lruvec->lrugen;
> --
> 2.18.4
>
Thanks for the fix!
Acked-by: Nhat Pham <nphamcs@gmail.com>
>
>
[-- Attachment #2: Type: text/html, Size: 2206 bytes --]
prev parent reply other threads:[~2023-05-09 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000004c3e6b05fb414be2@google.com>
2023-05-09 22:22 ` Tetsuo Handa
2023-05-09 23:12 ` Johannes Weiner
2023-05-09 23:59 ` Nhat Pham [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='CAKEwX=NsutS53FaSBAo12FQ+dTtpVBr2TR6mJN-bEKFZa4w4jQ@mail.gmail.com' \
--to=nphamcs@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzbot+3c6cac1550288f8e7060@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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