From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+a7f196a1dbf5e2c70568@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, Mike Rapoport <rppt@kernel.org>
Subject: Re: [syzbot] general protection fault in mpol_parse_str
Date: Mon, 31 Oct 2022 16:05:53 -0700 [thread overview]
Message-ID: <20221031160553.5afd9c461ebf34cfdcf70881@linux-foundation.org> (raw)
In-Reply-To: <00000000000078a84b05ec45e73b@google.com>
On Sun, 30 Oct 2022 12:57:43 -0700 syzbot <syzbot+a7f196a1dbf5e2c70568@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 4d48f589d294 Add linux-next specific files for 20221021
Thanks.
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=165e12da880000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2c4b7d600a5739a6
> dashboard link: https://syzkaller.appspot.com/bug?extid=a7f196a1dbf5e2c70568
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f10ff6880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=145f1ff2880000
does
memcpy((void*)0x20000100, "mpol=", 5);
syscall(__NR_mount, 0ul, 0x20000040ul, 0x20000080ul, 0ul, 0x20000100ul);
so I assume we've fallen afoul of the patch "vfs: parse: deal with zero
length string value"
(https://lkml.kernel.org/r/166365878918.39016.12757946948158123324.stgit@donald.themaw.net).
I have dropped that patch today so hopefully we're all good now.
>
> ...
>
prev parent reply other threads:[~2022-10-31 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 19:57 syzbot
2022-10-31 23:05 ` Andrew Morton [this message]
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=20221031160553.5afd9c461ebf34cfdcf70881@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=syzbot+a7f196a1dbf5e2c70568@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
all inboxes | Powered by JetHome®