From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: syzbot <syzbot+ccc0e1cfdb72b664f0d8@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
pasha.tatashin@soleen.com, syzkaller-bugs@googlegroups.com,
linux-usb@vger.kernel.org
Subject: Re: [syzbot] [mm?] kernel BUG in __page_table_check_zero (2)
Date: Tue, 5 Nov 2024 11:02:36 -0800 [thread overview]
Message-ID: <20241105110236.40819b7effad3f44de73dddf@linux-foundation.org> (raw)
In-Reply-To: <f94f3351-be53-4d61-a31a-2bb07925c5ad@rowland.harvard.edu>
On Tue, 5 Nov 2024 11:39:59 -0500 Alan Stern <stern@rowland.harvard.edu> wrote:
> On Mon, Nov 04, 2024 at 08:00:07PM -0800, Andrew Morton wrote:
> > On Wed, 30 Oct 2024 21:54:22 -0700 syzbot <syzbot+ccc0e1cfdb72b664f0d8@syzkaller.appspotmail.com> wrote:
> >
> > > Hello,
> > >
> > > syzbot found the following issue on:
> >
> > Thanks. I'm suspecting some USB issue - fault injection was used to
> > trigger a memory allocation failure and dec_usb_memory_use_count() ended
> > up freeing an in-use page. Could USB folks please have a look?
>
> Andrew, I'm not sure what to look for.
Thanks for looking.
> Can you read through
> usbdev_mmap() in drivers/usb/core/devio.c, along with the four short
> routines preceding it, and let us know if anything seems obviously
> wrong?
All I see is lots of USB code which I don't understand ;) It seems odd
that usbdev_mmap() calls dec_usb_memory_use_count() on some error
paths, but goes direct to usbfs_decrease_memory_usage() on others.
Did you try running the "C reproducer"?
next prev parent reply other threads:[~2024-11-05 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 4:54 syzbot
2024-11-05 4:00 ` Andrew Morton
2024-11-05 16:39 ` Alan Stern
2024-11-05 19:02 ` Andrew Morton [this message]
2024-11-05 20:42 ` Alan Stern
2024-11-05 21:30 ` Andrew Morton
2024-12-11 15:59 ` 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=20241105110236.40819b7effad3f44de73dddf@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+ccc0e1cfdb72b664f0d8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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