From: Yu Kuai <yukuai1@huaweicloud.com>
To: Guangwu Zhang <guazhang@redhat.com>,
linux-block@vger.kernel.org, io-uring@vger.kernel.org,
Jeff Moyer <jmoyer@redhat.com>, Ming Lei <ming.lei@redhat.com>,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [bug report] BUG: kernel NULL pointer dereference, address: 0000000000000048
Date: Wed, 10 May 2023 09:29:37 +0800 [thread overview]
Message-ID: <ecb54b0d-a90e-a2c9-dfe5-f5cec70be928@huaweicloud.com> (raw)
In-Reply-To: <CAGS2=YosaYaUTEMU3uaf+y=8MqSrhL7sYsJn8EwbaM=76p_4Qg@mail.gmail.com>
Hi,
在 2023/05/10 8:49, Guangwu Zhang 写道:
> Hi,
>
> We found this kernel NULL pointer issue with latest
> linux-block/for-next, please check it.
>
> Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
>
>
> [ 112.483804] BUG: kernel NULL pointer dereference, address: 0000000000000048
> [ 112.490809] #PF: supervisor read access in kernel mode
> [ 112.495976] #PF: error_code(0x0000) - not-present page
> [ 112.501141] PGD 800000044d20c067 P4D 800000044d20c067 PUD 4734d5067 PMD 0
> [ 112.508057] Oops: 0000 [#1] PREEMPT SMP PTI
> [ 112.512265] CPU: 24 PID: 7767 Comm: user-data Kdump: loaded Not
> tainted 6.4.0-rc1+ #1
> [ 112.520141] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380
> Gen10, BIOS U30 06/20/2018
> [ 112.528713] RIP: 0010:bfq_bio_bfqg+0x8/0x80
Can you show more details about addr2line result? It'll be much helpful.
Thanks,
Kuai
> [ 112.532925] Code: 6b 70 48 89 43 60 5b 5d c3 cc cc cc cc 0f 1f 44
> 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00
> 41 54 53 <48> 8b 46 48 48 89 fb 48 89 f7 48 85 c0 74 26 48 63 15 72 40
> 6b 01
> [ 112.551805] RSP: 0018:ffffaed687ef3b30 EFLAGS: 00010096
> [ 112.557058] RAX: ffff9a90f2600000 RBX: ffff9a90f2600000 RCX: 0000000000000001
> [ 112.564232] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff9a90f2600000
> [ 112.571408] RBP: ffff9a90c508d500 R08: ffff9a90e2b8a688 R09: ffff9a90e2b8a688
> [ 112.578581] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> [ 112.585756] R13: ffff9a90c508d500 R14: 0000000000000000 R15: 0000000000000000
> [ 112.592930] FS: 00007fe41b0f0880(0000) GS:ffff9a94afc00000(0000)
> knlGS:0000000000000000
> [ 112.601065] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 112.606842] CR2: 0000000000000048 CR3: 000000046346e005 CR4: 00000000007706e0
> [ 112.614016] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 112.621189] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [ 112.628362] PKRU: 55555554
> [ 112.631082] Call Trace:
> [ 112.633539] <TASK>
> [ 112.635650] bfq_bic_update_cgroup+0x2c/0x240
> [ 112.640033] bfq_init_rq+0xdd/0x670
> [ 112.643545] ? blk_rq_map_user_iov+0xc5/0x2f0
> [ 112.647931] bfq_insert_request.isra.0+0x5d/0x250
> [ 112.652663] bfq_insert_requests+0x59/0x80
> [ 112.656782] blk_mq_flush_plug_list+0x172/0x570
> [ 112.661342] blk_add_rq_to_plug+0x45/0x150
> [ 112.665462] nvme_uring_cmd_io+0x242/0x390 [nvme_core]
> [ 112.670652] io_uring_cmd+0x95/0x120
> [ 112.674250] io_issue_sqe+0x199/0x3d0
> [ 112.677932] io_submit_sqes+0x119/0x3d0
> [ 112.681788] __do_sys_io_uring_enter+0x2c2/0x470
> [ 112.686433] do_syscall_64+0x59/0x90
> [ 112.690031] ? exc_page_fault+0x65/0x150
> [ 112.693977] entry_SYSCALL_64_after_hwframe+0x72/0xdc
> [ 112.699057] RIP: 0033:0x7fe41ae3ee5d
> [ 112.702651] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e
> fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24
> 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 93 af 1b 00 f7 d8 64 89
> 01 48
> [ 112.721530] RSP: 002b:00007ffc6fdebc28 EFLAGS: 00000206 ORIG_RAX:
> 00000000000001aa
> [ 112.729143] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fe41ae3ee5d
> [ 112.736317] RDX: 0000000000000001 RSI: 0000000000000080 RDI: 0000000000000005
> [ 112.743492] RBP: 00007ffc6fdec730 R08: 0000000000000000 R09: 0000000000000080
> [ 112.750666] R10: 0000000000000001 R11: 0000000000000206 R12: 00007ffc6fdec848
> [ 112.757841] R13: 0000000000401346 R14: 0000000000403de8 R15: 00007fe41b32c000
> [ 112.765019] </TASK>
>
> .
>
next prev parent reply other threads:[~2023-05-10 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 0:49 [bug report] BUG: kernel NULL pointer dereference, address: 0000000000000048 Guangwu Zhang
2023-05-10 1:29 ` Yu Kuai [this message]
2023-05-10 1:49 ` Yu Kuai
2023-05-10 2:00 ` Yu Kuai
2023-05-10 2:17 ` Jens Axboe
2023-05-10 3:20 ` Yu Kuai
[not found] ` <CAGS2=YocNy9PkgRzzRdHAK1gGdjMxzA--PYS=sPrX_nCe4U6QA@mail.gmail.com>
2023-05-10 6:39 ` Ming Lei
2023-05-10 6:55 ` Yu Kuai
2023-05-10 12:08 ` Guangwu Zhang
2023-05-10 4:52 ` Guangwu Zhang
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=ecb54b0d-a90e-a2c9-dfe5-f5cec70be928@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=guazhang@redhat.com \
--cc=io-uring@vger.kernel.org \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.