From: <yang.yang29@zte.com.cn>
To: <willy@infradead.org>
Cc: <akpm@linux-foundation.org>, <hannes@cmpxchg.org>,
<bagasdotme@gmail.com>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<iamjoonsoo.kim@lge.com>, <ran.xiaokai@zte.com.cn>
Subject: Re: [PATCH linux-next v3] swap_state: update shadow_nodes for anonymous page
Date: Wed, 18 Jan 2023 20:17:54 +0800 (CST) [thread overview]
Message-ID: <202301182017545851044@zte.com.cn> (raw)
In-Reply-To: <Y8Wq3apsJh7keUVA@casper.infradead.org>
> i_lock is at offset 128 of struct inode, so that matches the dump.
> I believe that swapper_spaces never have ->host set, so I don't
> believe you've tested this patch since 51b8c1fe250d went in
> back in 2021.
You are totally right. I reproduce the panic in linux-next, and fix
it by patch v4. I should be more careful, since I used Linux 5.14
to test the patch which is a mistake.
Much apologies for the time wasted.
Thanks.
prev parent reply other threads:[~2023-01-18 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 9:36 yang.yang29
2023-01-16 19:51 ` Matthew Wilcox
2023-01-17 1:27 ` yang.yang29
2023-01-18 12:17 ` yang.yang29 [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=202301182017545851044@zte.com.cn \
--to=yang.yang29@zte.com.cn \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=willy@infradead.org \
/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