From: Matthew Wilcox <willy@infradead.org>
To: Tamir Duberstein <tamird@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
syzbot <syzbot+092bbab7da235a02a03a@syzkaller.appspotmail.com>,
asml.silence@gmail.com, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [syzbot] [io-uring?] KASAN: null-ptr-deref Write in sys_io_uring_register
Date: Wed, 4 Dec 2024 18:51:26 +0000 [thread overview]
Message-ID: <Z1Ckrl-gC3HpPj0W@casper.infradead.org> (raw)
In-Reply-To: <CAJ-ks9mfswrDNPjbakUsEtCTY-GbEoOGkOCrfAymDbDvUFgz5g@mail.gmail.com>
On Wed, Dec 04, 2024 at 01:39:37PM -0500, Tamir Duberstein wrote:
> > I thought I did, but when I ran it again just now, this test did catch
> > it. So there is coverage.
>
> Matthew, would you consider a patch that migrates the xarray tests to kunit?
how would that help? it's already a kernel module as well as being a
userspace testsuite. kunit just seemed to add useless boilerplate last
tie i looked.
next prev parent reply other threads:[~2024-12-04 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 13:56 [syzbot] [io-uring?] KASAN: null-ptr-deref Write in sys_io_uring_register syzbot
2024-12-04 15:01 ` Jens Axboe
2024-12-04 15:10 ` Jens Axboe
2024-12-04 15:21 ` Tamir Duberstein
2024-12-04 16:17 ` Jens Axboe
2024-12-04 16:25 ` Matthew Wilcox
2024-12-04 16:30 ` Tamir Duberstein
2024-12-04 18:39 ` Tamir Duberstein
2024-12-04 18:43 ` Jens Axboe
2024-12-04 18:51 ` Matthew Wilcox [this message]
2024-12-04 18:55 ` Tamir Duberstein
2024-12-04 16:30 ` Jens Axboe
2024-12-04 20:18 ` [syzbot] [mm] " syzbot
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=Z1Ckrl-gC3HpPj0W@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+092bbab7da235a02a03a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tamird@gmail.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.