From: Yosry Ahmed <yosryahmed@google.com>
To: Yu Zhao <yuzhao@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
syzbot+87c490fd2be656269b6a@syzkaller.appspotmail.com
Subject: Re: [PATCH mm-unstable v1] mm/mglru: make memcg_lru->lock irq safe
Date: Tue, 20 Jun 2023 13:19:38 -0700 [thread overview]
Message-ID: <CAJD7tkb=5kOiuYZxYQVCpjZZriCf2wrx9sgenrpP_Bct=GWfcw@mail.gmail.com> (raw)
In-Reply-To: <20230619193821.2710944-1-yuzhao@google.com>
On Mon, Jun 19, 2023 at 12:38 PM Yu Zhao <yuzhao@google.com> wrote:
>
> lru_gen_rotate_memcg() can happen in softirq if
> memory.soft_limit_in_bytes is set. This requires memcg_lru->lock to be
> irq safe.
>
> This problem only affects memcg v1.
>
> Reported-by: syzbot+87c490fd2be656269b6a@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=87c490fd2be656269b6a
> Fixes: e4dde56cd208 ("mm: multi-gen LRU: per-node lru_gen_folio lists")
> Signed-off-by: Yu Zhao <yuzhao@google.com>
> ---
> mm/vmscan.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 45d17c7cc555..27f90896f789 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -4759,10 +4759,11 @@ static void lru_gen_rotate_memcg(struct lruvec *lruvec, int op)
> {
> int seg;
> int old, new;
> + unsigned long flags;
> int bin = get_random_u32_below(MEMCG_NR_BINS);
> struct pglist_data *pgdat = lruvec_pgdat(lruvec);
>
> - spin_lock(&pgdat->memcg_lru.lock);
> + spin_lock_irqsave(&pgdat->memcg_lru.lock, flags);
Nit: I think it might be useful to add a comment here that this is
needed due to the call path from memcg_check_events() ->
mem_cgroup_update_tree() -- so that if that call path changes we can
come back and remove the irq-disablement.
FWIW:
Reviewed-by: Yosry Ahmed <yosryahmed@google.com>
>
> VM_WARN_ON_ONCE(hlist_nulls_unhashed(&lruvec->lrugen.list));
>
> @@ -4797,7 +4798,7 @@ static void lru_gen_rotate_memcg(struct lruvec *lruvec, int op)
> if (!pgdat->memcg_lru.nr_memcgs[old] && old == get_memcg_gen(pgdat->memcg_lru.seq))
> WRITE_ONCE(pgdat->memcg_lru.seq, pgdat->memcg_lru.seq + 1);
>
> - spin_unlock(&pgdat->memcg_lru.lock);
> + spin_unlock_irqrestore(&pgdat->memcg_lru.lock, flags);
> }
>
> void lru_gen_online_memcg(struct mem_cgroup *memcg)
> @@ -4810,7 +4811,7 @@ void lru_gen_online_memcg(struct mem_cgroup *memcg)
> struct pglist_data *pgdat = NODE_DATA(nid);
> struct lruvec *lruvec = get_lruvec(memcg, nid);
>
> - spin_lock(&pgdat->memcg_lru.lock);
> + spin_lock_irq(&pgdat->memcg_lru.lock);
>
> VM_WARN_ON_ONCE(!hlist_nulls_unhashed(&lruvec->lrugen.list));
>
> @@ -4821,7 +4822,7 @@ void lru_gen_online_memcg(struct mem_cgroup *memcg)
>
> lruvec->lrugen.gen = gen;
>
> - spin_unlock(&pgdat->memcg_lru.lock);
> + spin_unlock_irq(&pgdat->memcg_lru.lock);
> }
> }
>
> @@ -4845,7 +4846,7 @@ void lru_gen_release_memcg(struct mem_cgroup *memcg)
> struct pglist_data *pgdat = NODE_DATA(nid);
> struct lruvec *lruvec = get_lruvec(memcg, nid);
>
> - spin_lock(&pgdat->memcg_lru.lock);
> + spin_lock_irq(&pgdat->memcg_lru.lock);
>
> VM_WARN_ON_ONCE(hlist_nulls_unhashed(&lruvec->lrugen.list));
>
> @@ -4857,7 +4858,7 @@ void lru_gen_release_memcg(struct mem_cgroup *memcg)
> if (!pgdat->memcg_lru.nr_memcgs[gen] && gen == get_memcg_gen(pgdat->memcg_lru.seq))
> WRITE_ONCE(pgdat->memcg_lru.seq, pgdat->memcg_lru.seq + 1);
>
> - spin_unlock(&pgdat->memcg_lru.lock);
> + spin_unlock_irq(&pgdat->memcg_lru.lock);
> }
> }
>
> --
> 2.41.0.185.g7c58973941-goog
>
>
prev parent reply other threads:[~2023-06-20 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 19:38 Yu Zhao
2023-06-20 20:19 ` Yosry Ahmed [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='CAJD7tkb=5kOiuYZxYQVCpjZZriCf2wrx9sgenrpP_Bct=GWfcw@mail.gmail.com' \
--to=yosryahmed@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+87c490fd2be656269b6a@syzkaller.appspotmail.com \
--cc=yuzhao@google.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