From: David Hildenbrand <david@redhat.com>
To: Kees Cook <keescook@chromium.org>,
Murphy Zhou <jencce.kernel@gmail.com>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-Next <linux-next@vger.kernel.org>
Subject: Re: linux-next: panic on 20220307 tree
Date: Thu, 10 Mar 2022 17:54:04 +0100 [thread overview]
Message-ID: <40f2a251-b844-9c6e-3e36-795433482998@redhat.com> (raw)
In-Reply-To: <202203100825.8EAF86328B@keescook>
On 10.03.22 17:29, Kees Cook wrote:
> On Tue, Mar 08, 2022 at 10:44:57AM +0800, Murphy Zhou wrote:
>> Hi,
>>
>> Hit this shortly after build the next tree and reboot.
>>
>> [ 72.985994] ------------[ cut here ]------------
>> [ 72.986023] ------------[ cut here ]------------
>> [ 73.009468] kernel BUG at include/linux/swapops.h:258!
>> [ 73.033065] kernel BUG at include/linux/swapops.h:258!
>
> This is in here:
>
> static inline struct page *pfn_swap_entry_to_page(swp_entry_t entry)
> {
> struct page *p = pfn_to_page(swp_offset(entry));
>
> /*
> * Any use of migration entries may only occur while the
> * corresponding page is locked
> */
> BUG_ON(is_migration_entry(entry) && !PageLocked(p));
>
> return p;
> }
>
> Hugh, David, Andrew, might any of the recent mm/memory.c work caused
> problems in here? (Or is this already fixed?)
Maybe related to:
https://lore.kernel.org/all/8f419d19-c83d-bbcd-8936-2d64ced7464c@google.com/T/#u
which should be fixed now.
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2022-03-10 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 2:44 linux-next: panic on 20220307 tree Murphy Zhou
2022-03-10 16:29 ` Kees Cook
2022-03-10 16:54 ` David Hildenbrand [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=40f2a251-b844-9c6e-3e36-795433482998@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jencce.kernel@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-next@vger.kernel.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