From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Eric Biggers <ebiggers3@gmail.com>, Michal Hocko <mhocko@kernel.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
syzbot <syzbot+151de3f2be6b40ac8026@syzkaller.appspotmail.com>,
gregkh@linuxfoundation.org, kstewart@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
pombredanne@nexb.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, linux-fsdevel@vger.kernel.org
Subject: Re: general protection fault in kernfs_kill_sb
Date: Fri, 20 Apr 2018 14:29:39 +0900 [thread overview]
Message-ID: <201804200529.w3K5TdvM009951@www262.sakura.ne.jp> (raw)
In-Reply-To: <20180420033450.GC686@sol.localdomain>
Eric Biggers wrote:
> But, there is still a related bug: when mounting sysfs, if register_shrinker()
> fails in sget_userns(), then kernfs_kill_sb() gets called, which frees the
> 'struct kernfs_super_info'. But, the 'struct kernfs_super_info' is also freed
> in kernfs_mount_ns() by:
>
> sb = sget_userns(fs_type, kernfs_test_super, kernfs_set_super, flags,
> &init_user_ns, info);
> if (IS_ERR(sb) || sb->s_fs_info != info)
> kfree(info);
> if (IS_ERR(sb))
> return ERR_CAST(sb);
>
> I guess the problem is that sget_userns() shouldn't take ownership of the 'info'
> if it returns an error -- but, it actually does if register_shrinker() fails,
> resulting in a double free.
>
> Here is a reproducer and the KASAN splat. This is on Linus' tree (87ef12027b9b)
> with vfs/for-linus merged in.
I'm waiting for response from Michal Hocko regarding
http://lkml.kernel.org/r/201804111909.EGC64586.QSFLFJFOVHOOtM@I-love.SAKURA.ne.jp .
>
> #define _GNU_SOURCE
> #include <fcntl.h>
> #include <sched.h>
> #include <stdio.h>
> #include <stdlib.h>
> #include <sys/mount.h>
> #include <sys/stat.h>
> #include <unistd.h>
>
> int main()
> {
> int fd, i;
> char buf[16];
>
> unshare(CLONE_NEWNET);
> system("echo N > /sys/kernel/debug/failslab/ignore-gfp-wait");
> system("echo 0 | tee /sys/kernel/debug/fail*/verbose");
> fd = open("/proc/thread-self/fail-nth", O_WRONLY);
> for (i = 0; ; i++) {
> write(fd, buf, sprintf(buf, "%d", i));
> mount("sysfs", "mnt", "sysfs", 0, NULL);
> umount("mnt");
> }
> }
next prev parent reply other threads:[~2018-04-20 5:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94eb2c0546040ebb4d0568cc6bdb@google.com>
2018-04-02 10:40 ` general protection fault in kernfs_kill_sb Tetsuo Handa
2018-04-02 14:34 ` Al Viro
2018-04-20 2:44 ` Eric Biggers
2018-04-20 3:34 ` Eric Biggers
2018-04-20 5:29 ` Tetsuo Handa [this message]
2018-04-20 7:31 ` Michal Hocko
2018-04-20 17:55 ` Eric Biggers
2018-05-02 10:37 ` Tetsuo Handa
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=201804200529.w3K5TdvM009951@www262.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=ebiggers3@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=pombredanne@nexb.com \
--cc=syzbot+151de3f2be6b40ac8026@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@ZenIV.linux.org.uk \
/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).