From: Su Yue <l@damenly.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Brian Foster <bfoster@redhat.com>, linux-bcachefs@vger.kernel.org
Subject: Re: [BUG] general protection fault, probably for non-canonical address 0x280766500040001: 0000 [#1] PREEMPT SMP PTI
Date: Wed, 17 Jan 2024 12:20:55 +0800 [thread overview]
Message-ID: <bk9k60zw.fsf@damenly.org> (raw)
In-Reply-To: <dbqhxiv7kxbaeilxyyqzqqpjlaobxh262u7czkg5koec2w35p4@2oznjzf466no>
On Tue 16 Jan 2024 at 12:33, Kent Overstreet
<kent.overstreet@linux.dev> wrote:
> On Tue, Jan 16, 2024 at 12:24:48PM -0500, Brian Foster wrote:
>> On Tue, Jan 16, 2024 at 12:03:09PM -0500, Kent Overstreet
>> wrote:
>> > On Tue, Jan 16, 2024 at 10:33:08AM -0500, Brian Foster wrote:
>> > > Hi Kent,
>> > >
>> > > JFYI, I'm seeing the following splat pretty reliably via
>> > > generic/361 on
>> > > an 80xcpu test box. The CI doesn't seem to produce this
>> > > failure for
>> > > whatever reason. This bisects down to commit 023f9ac9f70f
>> > > ("bcachefs:
>> > > Delete dio read alignment check"), before which the test
>> > > still fails but
>> > > the kernel doesn't explode.
>> > >
>> > > Brian
>> > >
>> >
>> > Can you test the following?
>> >
>>
>> Still blows up... repeated a couple times to be sure.
>
> That sounds like a driver bug then - what driver?
I think it's not a drive bug. It's related to bcachefs block_size.
I can reproduce it by running generic/361 with block_size 4096.
The test devices are normal qemu disks backing by files in host.
The bug disappears after hanging mkfs block_size to 512.
--
Su
next prev parent reply other threads:[~2024-01-17 4:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 15:33 [BUG] general protection fault, probably for non-canonical address 0x280766500040001: 0000 [#1] PREEMPT SMP PTI Brian Foster
2024-01-16 16:37 ` Kent Overstreet
2024-01-16 17:03 ` Kent Overstreet
2024-01-16 17:24 ` Brian Foster
2024-01-16 17:33 ` Kent Overstreet
2024-01-17 4:20 ` Su Yue [this message]
2024-01-17 13:07 ` Brian Foster
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=bk9k60zw.fsf@damenly.org \
--to=l@damenly.org \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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