[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YPlmMnZKgkcLderp@casper.infradead.org>
Date: Thu, 22 Jul 2021 13:36:02 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Zhouyi Zhou <zhouzhouyi@...il.com>
Cc: Chris Clayton <chris2553@...glemail.com>,
Oleksandr Natalenko <oleksandr@...alenko.name>,
Miaohe Lin <linmiaohe@...wei.com>,
Boqun Feng <boqun.feng@...il.com>, paulmck@...nel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
stable@...r.kernel.org, Chris Rankin <rankincj@...il.com>,
Josh Triplett <josh@...htriplett.org>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lai Jiangshan <jiangshanlai@...il.com>,
Joel Fernandes <joel@...lfernandes.org>,
rcu <rcu@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux-MM <linux-mm@...ck.org>,
"Huang, Ying" <ying.huang@...el.com>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: linux-5.13.2: warning from kernel/rcu/tree_plugin.h:359
On Thu, Jul 22, 2021 at 04:57:57PM +0800, Zhouyi Zhou wrote:
> Thanks for reviewing,
>
> What I have deduced from the dmesg is:
> In function do_swap_page,
> after invoking
> 3385 si = get_swap_device(entry); /* rcu_read_lock */
> and before
> 3561 out:
> 3562 if (si)
> 3563 put_swap_device(si);
> The thread got scheduled out in
> 3454 locked = lock_page_or_retry(page, vma->vm_mm, vmf->flags);
>
> I am only familiar with Linux RCU subsystem, hope mm people can solve our
> confusions.
I don't understamd why you're still talking. The problem is understood.
You need to revert the unnecessary backport of 2799e77529c2 and
2efa33fc7f6e
Powered by blists - more mailing lists