From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+b636fe4123f39f69c35b@syzkaller.appspotmail.com>
Cc: linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: Re: kernel panic: stack is corrupted in mpol_to_str
Date: Thu, 26 Mar 2020 20:21:00 +0900 [thread overview]
Message-ID: <56f09db2-7e46-74b5-09c3-4873b3acc56c@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <000000000000276fa005a1b8aeb5@google.com>
Two reproducers have only offset difference.
1c1
< // https://syzkaller.appspot.com/bug?id=95622e9b1d82dd9e1368d04b2d11f9daa102b685
---
> // https://syzkaller.appspot.com/bug?id=b642faac21312365cd30cc83ec73b2a05f73bf8a
134,142c134,142
< memcpy((void*)0x20000000, "tmpfs\000", 6);
< memcpy((void*)0x20002140, "./file0\000", 8);
< memcpy((void*)0x200000c0, "mpol", 4);
< *(uint8_t*)0x200000c4 = 0x3d;
< memcpy((void*)0x200000c5, "prefer", 6);
< *(uint8_t*)0x200000cb = 0x3a;
< *(uint8_t*)0x200000cc = 0x2c;
< *(uint8_t*)0x200000cd = 0;
< syz_mount_image(0x20000000, 0x20002140, 0, 0, 0, 0, 0x200000c0);
---
> memcpy((void*)0x200000c0, "tmpfs\000", 6);
> memcpy((void*)0x20000000, "./file0\000", 8);
> memcpy((void*)0x20000100, "mpol", 4);
> *(uint8_t*)0x20000104 = 0x3d;
> memcpy((void*)0x20000105, "prefer", 6);
> *(uint8_t*)0x2000010b = 0x3a;
> *(uint8_t*)0x2000010c = 0x2c;
> *(uint8_t*)0x2000010d = 0;
> syz_mount_image(0x200000c0, 0x20000000, 0, 0, 0, 0, 0x20000100);
#syz dup: KASAN: stack-out-of-bounds Write in mpol_to_str
prev parent reply other threads:[~2020-03-26 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 2:24 kernel panic: stack is corrupted in mpol_to_str syzbot
2020-03-26 11:21 ` Tetsuo Handa [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=56f09db2-7e46-74b5-09c3-4873b3acc56c@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=linux-mm@kvack.org \
--cc=syzbot+b636fe4123f39f69c35b@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;
as well as URLs for NNTP newsgroup(s).