[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180408060140.GB16007@bombadil.infradead.org>
Date: Sat, 7 Apr 2018 23:01:40 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: syzbot <syzbot+75397ee3df5c70164154@...kaller.appspotmail.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
syzkaller-bugs@...glegroups.com, Al Viro <viro@...iv.linux.org.uk>
Subject: Re: WARNING in kmem_cache_free
On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote:
> On Fri, Apr 6, 2018 at 3:24 PM, syzbot
> <syzbot+75397ee3df5c70164154@...kaller.appspotmail.com> wrote:
> > Unfortunately, I don't have any reproducer for this crash yet.
>
> Interesting type of bug, I think we see this for the first time.
Can you focus syzbot to try to find a reproducer? This seems to be
produced by calling mount() with a pathname that's somewhere between,
say, 3950 & 4100 bytes long from a compat 32-bit task.
Powered by blists - more mailing lists