mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Li Wang <liwang@kylinos.cn>
To: Jingbo Xu <jefflexu@linux.alibaba.com>,
	Miklos Szeredi <miklos@szeredi.hu>
Cc: Joanne Koong <joannelkoong@gmail.com>,
	Bernd Schubert <bernd@bsbernd.com>,
	fuse-devel@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fuse: fix kernel NULL pointer dereference in fuse_uring_add_to_pq()
Date: Thu, 23 Apr 2026 09:52:44 +0800	[thread overview]
Message-ID: <c26c666f-2d6e-44e1-8974-d9e46e329ee1@kylinos.cn> (raw)
In-Reply-To: <e6077b7c-160c-4444-8ab8-ccab8b14ac27@linux.alibaba.com>

Hi Jingbo,

On 22/04/2026 19:18, Jingbo Xu wrote:
> 
> 
> On 4/22/26 6:36 PM, Li Wang wrote:
>> A kernel NULL pointer dereference was triggered when testing the
>> 'fuse over io_uring' feature with passthrough_ll. The call trace
>> is as follows:
>>   BUG: kernel NULL pointer dereference, address: 0000000000000878
>>   RIP: 0010:fuse_uring_add_req_to_ring_ent+0x89/0xd0 [fuse]
>>   Call Trace:
>>   <TASK>
>>   fuse_uring_queue_fuse_req+0x82/0x100 [fuse]
>>   fuse_chan_send+0xe6/0x180 [fuse]
> 
> I don't see fuse_chan_send() in upstream kernel.  I think you are
> testing kernel with this patchset[1] applied?
> 
> [1] https://lore.kernel.org/all/20260416091658.462783-1-mszeredi@redhat.com/
> 

The test is based on 
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#for-next

Thanks,
Li

  reply	other threads:[~2026-04-23  1:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 10:36 Li Wang
2026-04-22 11:18 ` Jingbo Xu
2026-04-23  1:52   ` Li Wang [this message]
2026-04-22 11:39 ` Bernd Schubert
2026-04-23  2:04   ` Li Wang
2026-04-22 19:18 ` Joanne Koong
2026-04-23  6:44   ` Li Wang
2026-04-23  7:17     ` Miklos Szeredi

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=c26c666f-2d6e-44e1-8974-d9e46e329ee1@kylinos.cn \
    --to=liwang@kylinos.cn \
    --cc=bernd@bsbernd.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=jefflexu@linux.alibaba.com \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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®