From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+75397ee3df5c70164154@syzkaller.appspotmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in kmem_cache_free
Date: Sun, 8 Apr 2018 06:59:13 +0100 [thread overview]
Message-ID: <20180408055900.GH30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CACT4Y+adiXih0-jfNGHgf1kEQ2=KLY5NdX-87BTDbrQgEAHc9g@mail.gmail.com>
On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote:
> Interesting type of bug, I think we see this for the first time.
>
> Al, do you see how this can happen?
putname() on something that hasn't come from getname(). Short
of reproducer, I don't see what can be done - it can be any
kind of memory corruption. We have
return filename_lookup(dfd, getname_flags(name, flags, empty),
flags, path, NULL);
with filename_lookup() hitting
putname(name);
return retval;
on the way out (and seeing refcount 1, at that, so it hasn't ended
up in audit context). And object it's trying to free is not something
getname_flags() has allocated.
next prev parent reply other threads:[~2018-04-08 6:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 13:24 WARNING in kmem_cache_free syzbot
2018-04-06 13:33 ` Dmitry Vyukov
2018-04-08 3:16 ` Use struct page for filename Matthew Wilcox
2018-04-08 4:42 ` Al Viro
2018-04-08 5:59 ` Al Viro [this message]
2018-04-08 6:01 ` WARNING in kmem_cache_free Matthew Wilcox
2018-04-08 10:26 ` Dmitry Vyukov
2018-04-08 11:18 ` Dmitry Vyukov
2018-04-08 15:31 ` Stephan Müller
2018-04-08 15:41 ` Dmitry Vyukov
2018-04-08 19:07 ` [PATCH] crypto: DRBG - guard uninstantion by lock Stephan Müller
2018-04-08 22:46 ` Theodore Y. Ts'o
2018-04-08 22:46 ` Theodore Y. Ts'o
2018-04-09 5:40 ` Stephan Mueller
2018-04-09 7:57 ` Dmitry Vyukov
2018-04-10 15:23 ` Dmitry Vyukov
2018-04-10 15:35 ` Stephan Mueller
2018-04-11 12:29 ` Dmitry Vyukov
2018-04-11 12:59 ` Stephan Mueller
2018-04-11 14:26 ` Stephan Müller
2018-04-11 14:31 ` [PATCH] crypto: drbg - set freed buffers to NULL Stephan Müller
2018-04-11 17:29 ` Eric Biggers
2018-04-11 17:29 ` Eric Biggers
2018-04-12 6:40 ` Stephan Müller
2018-04-20 16:54 ` Herbert Xu
2018-04-20 16:54 ` Herbert Xu
2018-04-11 17:09 ` [PATCH] crypto: DRBG - guard uninstantion by lock Dmitry Vyukov
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=20180408055900.GH30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+75397ee3df5c70164154@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 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.