From: David Hildenbrand <david@redhat.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Pengfei Xu <pengfei.xu@intel.com>,
rdunlap@infradead.org, akpm@linux-foundation.org,
heng.su@intel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, lkp@intel.com
Subject: Re: [Syzkaller & bisect] There is BUG: unable to handle kernel paging request in fuse_copy_one in intel-6.8-rc2
Date: Wed, 31 Jan 2024 11:54:25 +0100 [thread overview]
Message-ID: <77ace07b-3f84-46ac-8a29-e782d7f60078@redhat.com> (raw)
In-Reply-To: <ZbolZRw9yFk9jLB6@kernel.org>
On 31.01.24 11:48, Mike Rapoport wrote:
> On Wed, Jan 31, 2024 at 10:15:11AM +0100, David Hildenbrand wrote:
>> On 31.01.24 03:01, Pengfei Xu wrote:
>>> Hi Mike,
>>>
>>> Greeting!
>>>
>>> There is "unable to handle kernel paging request in fuse_copy_one" BUG in
>>> intel-6.8-rc2:
>>>
>>> All detailed info: https://github.com/xupengfe/syzkaller_logs/tree/main/240130_184751_fuse_copy_one
>>> Syzkaller reproduced code: https://github.com/xupengfe/syzkaller_logs/blob/main/240130_184751_fuse_copy_one/repro.c
>>> Syzkaller repro syscall steps: https://github.com/xupengfe/syzkaller_logs/blob/main/240130_184751_fuse_copy_one/repro.prog
>>> Bisect info: https://github.com/xupengfe/syzkaller_logs/blob/main/240130_184751_fuse_copy_one/bisect_info.log
>>> Issue dmesg: https://github.com/xupengfe/syzkaller_logs/blob/main/240130_184751_fuse_copy_one/41bccc98fb7931d63d03f326a746ac4d429c1dd3_dmesg.log
>>> bzImage: https://github.com/xupengfe/syzkaller_logs/raw/main/240130_184751_fuse_copy_one/bzImage_v6.8-rc2.tar.gz
>>> Kconfig(make olddefconfig): https://github.com/xupengfe/syzkaller_logs/blob/main/240130_184751_fuse_copy_one/kconfig_origin
>>>
>>> Bisected and found first bad commit is:
>>> b758fe6df50da mm/secretmem: make it on by default
>>
>> Sounds like we manage to access a page that has its direct map removed --
>> either because it's actual secretmem memory, or because we fail to restore
>> the direct map.
>
> Judging by the repro code and the registers, it's an access to secretmem.
>
> The call
> syscall(__NR_write, /*fd=*/r[0], /*arg=*/0x20000040ul, /*len=*/0x50ul);
>
> will eventually get to
>
> memcpy(0xffff88800e2afa80, 0xffff8880119a5040, 0x0000000000000010)
>
> and I think that 0x20000040 in repro address space maps to
> 0xffff8880119a5040 in the direct map.
>
> So it looks like secretmem actually works :)
Good. How can we prevent triggering BUGs? The write system call should
fail gracefully (and I thought it would).
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-01-31 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 2:01 [Syzkaller & bisect] There is BUG: unable to handle kernel paging request in fuse_copy_one in intel-6.8-rc2 Pengfei Xu
2024-01-31 9:15 ` David Hildenbrand
2024-01-31 10:48 ` Mike Rapoport
2024-01-31 10: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=77ace07b-3f84-46ac-8a29-e782d7f60078@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=heng.su@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=pengfei.xu@intel.com \
--cc=rdunlap@infradead.org \
--cc=rppt@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;
as well as URLs for NNTP newsgroup(s).