From: Sachin Sant <sachinp@linux.ibm.com>
To: Lorenzo Stoakes <lstoakes@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-mm@kvack.org, open list <linux-kernel@vger.kernel.org>
Subject: Re: [powerpc] Kernel crash while running LTP (bisected)
Date: Tue, 17 Oct 2023 19:00:20 +0530 [thread overview]
Message-ID: <93251CB3-D144-44F5-A482-0051A398E643@linux.ibm.com> (raw)
In-Reply-To: <84a6c480-f29b-4a73-bbb0-4908145dc4db@lucifer.local>
> On 17-Oct-2023, at 4:35 PM, Lorenzo Stoakes <lstoakes@gmail.com> wrote:
>
> On Tue, Oct 17, 2023 at 02:46:07PM +0530, Sachin Sant wrote:
>> While running LTP tests (getpid02) on a Power10 server booted with
>> 6.6.0-rc6-next-20231016 following crash was seen:
>>
>> [ 76.386628] Kernel attempted to read user page (d8) - exploit attempt? (uid: 0)
>> [ 76.386649] BUG: Kernel NULL pointer dereference on read at 0x000000d8
>> [ 76.386653] Faulting instruction address: 0xc0000000004cda90
>> [ 76.386658] Oops: Kernel access of bad area, sig: 11 [#1]
> [snip]
>>
>> Git bisect points to following patch
>>
>> commit 1db41d29b79ad271674081c752961edd064bbbac
>> mm: perform the mapping_map_writable() check after call_mmap()
>>
>> Reverting the patch allows the test to complete.
>>
>> - Sachin
>
> Hi Sachin,
>
> Thanks for the report but this was triggered in another test previously and
> has been fixed already (apologies for the inconvenience!) see [0]. Andrew
> took the -fix patch and applied to mm-unstable, this should wend its way to
> -next in the meantime.
Ah, thank you. Yes the fix works for me.
- Sachin
prev parent reply other threads:[~2023-10-17 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 9:16 Sachin Sant
2023-10-17 11:05 ` Lorenzo Stoakes
2023-10-17 13:30 ` Sachin Sant [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=93251CB3-D144-44F5-A482-0051A398E643@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lstoakes@gmail.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