From: Alexander Sverdlin <alexander.sverdlin@nokia.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Alexander Duyck <alexanderduyck@fb.com>,
Matthew Wilcox <willy@infradead.org>,
Hugh Dickins <hughd@google.com>, Yu Zhao <yuzhao@google.com>,
Mel Gorman <mgorman@techsingularity.net>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
Sasha Levin <sashal@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: mm: swap: locking in release_pages()
Date: Tue, 5 Apr 2022 13:36:09 +0200 [thread overview]
Message-ID: <dc5eb22d-5389-bacb-3756-253e774a8394@nokia.com> (raw)
In-Reply-To: <YkwdRnuQBjoJ01YK@dhcp22.suse.cz>
Hello Michal,
thanks for the quick reply!
On 05/04/2022 12:43, Michal Hocko wrote:
>> 1. Crash of v5.4.170 on an ARM32 machine:
>>
>> Unable to handle kernel NULL pointer dereference at virtual address 00000104
>> pgd = e138149d
>> [00000104] *pgd=84d2fd003, *pmd=8ffd6f003
>> Internal error: Oops: a07 [#1] PREEMPT SMP ARM
>> ...
>> CPU: 1 PID: 6172 Comm: AaSysInfoRColle Tainted: G B O 5.4.170-... #1
>> Hardware name: Keystone
>> PC is at release_pages+0x194/0x358
>> LR is at release_pages+0x10c/0x358
> Which LOC does this correspond to? (faddr2line should give you a nice
> output).
Sorry, I forgot this info in the initial report:
this is indeed the del_page_from_lru_list() in this crash. So it's either two different ->lru_lock
or some other code path doesn't take lru_lock at all...
--
Best regards,
Alexander Sverdlin.
next prev parent reply other threads:[~2022-04-05 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 10:20 Alexander Sverdlin
2022-04-05 10:43 ` Michal Hocko
2022-04-05 11:36 ` Alexander Sverdlin [this message]
2022-04-05 11:45 ` Michal Hocko
2022-04-05 14:00 ` Alexander Sverdlin
2022-04-05 14:17 ` Michal Hocko
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=dc5eb22d-5389-bacb-3756-253e774a8394@nokia.com \
--to=alexander.sverdlin@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=alexanderduyck@fb.com \
--cc=hughd@google.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=npiggin@gmail.com \
--cc=sashal@kernel.org \
--cc=willy@infradead.org \
--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