From: Matthew Wilcox <willy@infradead.org>
To: Chenyuan Yang <chenyuan0y@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, syzkaller@googlegroups.com,
Zijie Zhao <zzjas98@gmail.com>,
John Hubbard <jhubbard@nvidia.com>
Subject: Re: [Linux Kernel Bug][mm/gup] 3 Warning Crashes: kmalloc bug in gup_test_ioctl, is_valid_gup_args, pin_user_pages_fast
Date: Fri, 26 Jan 2024 18:34:54 +0000 [thread overview]
Message-ID: <ZbP7ThrtxhIBJChT@casper.infradead.org> (raw)
In-Reply-To: <CALGdzuo7V-3-US9U+rjyBfmZD=d-gUfAxJejsTUsmnSZNDnh5A@mail.gmail.com>
On Fri, Jan 26, 2024 at 11:31:26AM -0600, Chenyuan Yang wrote:
> In this context, I would like to seek your valued opinion. Do you
> believe it would be more prudent to avoid fuzz testing the
> `gup_test_ioctl`, or are the warnings in `gup_test_ioctl` an
> anticipated outcome?
It seems like a waste of time. Debian certainly disables it, so
unless you can find a distro who enables it, I wouldn't bother.
> It seems that `gup_test_ioctl` can indeed be exposed in the kernel by
> accessing /sys/kernel/debug/gup_test.
If someone wants to fix these things, they can, but it just doesn't
seem worth doing. Part of the art of fuzz testing is finding things
that are worth testing.
next prev parent reply other threads:[~2024-01-26 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 17:04 [Linux Kernel Bug][mm/gup] 3 Warning Crashes: kmalloc bug in gup_test_ioctl, is_valid_gup_args, pin_user_pages_fast Chenyuan Yang
2024-01-26 17:11 ` Matthew Wilcox
2024-01-26 17:31 ` Chenyuan Yang
2024-01-26 18:34 ` Matthew Wilcox [this message]
2024-01-26 19:08 ` John Hubbard
2024-01-26 19:23 ` Chenyuan Yang
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=ZbP7ThrtxhIBJChT@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=chenyuan0y@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller@googlegroups.com \
--cc=zzjas98@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.