From: Genes Lists <lists@sapience.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: song@kernel.org, yukuai3@huawei.com, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, linux@leemhuis.info
Subject: Re: md-raid 6.11.8 page fault oops
Date: Tue, 19 Nov 2024 08:31:02 -0500 [thread overview]
Message-ID: <ef8bd4f9308dbf941076b2f7bd8a81590a09aa5e.camel@sapience.com> (raw)
In-Reply-To: <Zzx34Mm5K42GWyKj@li-bb2b2a4c-3307-11b2-a85c-8fa5c3a69313.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1864 bytes --]
On Tue, 2024-11-19 at 17:04 +0530, Ojaswin Mujoo wrote:
> >
...
> > (gdb) list *(rb_first+0x13)
> > 0xffffffff81de1af3 is in rb_first (lib/rbtree.c:473).
> > 468 struct rb_node *n;
> > 469
> > 470 n = root->rb_node;
> > 471 if (!n)
> > 472 return NULL;
> > 473 while (n->rb_left)
>
> Now this looks strange, we already make sure n is not NULL and then
> somehow this line ends up in
>
> BUG: unable to handle page fault for address: 0000000000200010
>
> Now, decoding the code with an x86 vmlinux, I see the fauling opcode
> faulting:
>
> Code starting with the faulting instruction
> ===========================================
> 0: 0f 1f 80 00 00 00 00 nopl 0x0(%rax)
> 7: 90 nop
> 8: 90 nop
> 9: 90 nop
> a: 90 nop
> b: 90 nop
> c: 90 nop
> d: 90 nop
> e: 90 nop
> f: 90 nop
>
> Now RAX is 0x200000 but I don't think the nopl instruction should
> have resulted
> in a mem access AFA my limited understanding of x86 ISA goes.
>
> I also don't see nopl in my vmlinux in rb_first, my binary being
> compiled with
> gcc 8.5. Are you by chance using clang or higher version or higher
> optimization in gcc.
>
> Regards,
> ojaswin
I am using Arch toolchain with
gcc 14.2.1+r134+gab884fffe3fc-1
I do not set CFLAGS_KERNEL so compile options are the default.
thanks
gene
[-- Attachment #1.2: Type: text/html, Size: 4349 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-19 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 12:12 Genes Lists
2024-11-15 17:55 ` Song Liu
2024-11-16 3:34 ` Yu Kuai
2024-11-16 12:01 ` Genes Lists
2024-11-18 10:34 ` Mikulas Patocka
2024-11-19 11:49 ` Yu Kuai
2024-11-17 17:23 ` Genes Lists
2024-11-18 1:14 ` Yu Kuai
2024-11-20 11:48 ` md-raid 6.11.8 page fault oops - *bad memory* please ignore Genes Lists
2024-11-19 11:34 ` md-raid 6.11.8 page fault oops Ojaswin Mujoo
2024-11-19 13:31 ` Genes Lists [this message]
2024-11-20 10:18 ` Ojaswin Mujoo
2024-11-20 11:04 ` Genes Lists
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=ef8bd4f9308dbf941076b2f7bd8a81590a09aa5e.camel@sapience.com \
--to=lists@sapience.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=ojaswin@linux.ibm.com \
--cc=song@kernel.org \
--cc=tytso@mit.edu \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®