From: Tejun Heo <tj@kernel.org>
To: almasrymina@google.com,
syzbot <syzbot+cac0c4e204952cf449b1@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, andriin@fb.com, ast@kernel.org,
bpf@vger.kernel.org, cgroups@vger.kernel.org,
christian@brauner.io, daniel@iogearbox.net, hannes@cmpxchg.org,
kafai@fb.com, linux-kernel@vger.kernel.org, lizefan@huawei.com,
netdev@vger.kernel.org, sfr@canb.auug.org.au,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
yhs@fb.com
Subject: Re: KASAN: slab-out-of-bounds Read in cgroup_file_notify
Date: Thu, 12 Mar 2020 14:28:26 -0400 [thread overview]
Message-ID: <20200312182826.GG79873@mtj.duckdns.org> (raw)
In-Reply-To: <00000000000041c6c205a08225dc@google.com>
On Tue, Mar 10, 2020 at 08:55:14AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: c99b17ac Add linux-next specific files for 20200225
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1610d70de00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=6b7ebe4bd0931c45
> dashboard link: https://syzkaller.appspot.com/bug?extid=cac0c4e204952cf449b1
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1242e1fde00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1110d70de00000
>
> The bug was bisected to:
>
> commit 6863de00e5400b534cd4e3869ffbc8f94da41dfc
> Author: Mina Almasry <almasrymina@google.com>
> Date: Thu Feb 20 03:55:30 2020 +0000
>
> hugetlb_cgroup: add accounting for shared mappings
Mina, can you please take a look at this?
Thanks.
--
tejun
next prev parent reply other threads:[~2020-03-12 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 15:55 KASAN: slab-out-of-bounds Read in cgroup_file_notify syzbot
2020-03-12 18:28 ` Tejun Heo [this message]
2020-03-12 21:06 ` Mina Almasry
2020-03-12 21:06 ` Mina Almasry
2020-03-13 22:43 ` Mina Almasry
2020-03-13 22:43 ` Mina Almasry
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=20200312182826.GG79873@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=christian@brauner.io \
--cc=daniel@iogearbox.net \
--cc=hannes@cmpxchg.org \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=songliubraving@fb.com \
--cc=syzbot+cac0c4e204952cf449b1@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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.