LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: viro@ZenIV.linux.org.uk
Cc: syzbot+7a1cff37dbbef9e7ba4c@syzkaller.appspotmail.com,
akpm@linux-foundation.org, dhowells@redhat.com,
ebiederm@xmission.com, ebiggers3@gmail.com, gs051095@gmail.com,
ktkhai@virtuozzo.com, linux-kernel@vger.kernel.org,
oleg@redhat.com, pasha.tatashin@oracle.com, riel@redhat.com,
rppt@linux.vnet.ibm.com, syzkaller-bugs@googlegroups.com,
wangkefeng.wang@huawei.com
Subject: Re: KASAN: use-after-free Read in alloc_pid
Date: Tue, 10 Apr 2018 23:33:41 +0900 [thread overview]
Message-ID: <201804102333.BCC87582.MFHFOQFOOJLVtS@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <000000000000a45f6f05697f173b@google.com>
syzbot wrote:
> syzbot has found reproducer for the following crash on upstream commit
> c18bb396d3d261ebbb4efbc05129c5d354c541e4 (Tue Apr 10 00:04:10 2018 +0000)
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
> syzbot dashboard link:
> https://syzkaller.appspot.com/bug?extid=7a1cff37dbbef9e7ba4c
>
While we are waiting for
rpc_pipefs: fix double-dput()
rpc_pipefs: deal with early sget() failures
kernfs: deal with early sget() failures
procfs: deal with early sget() failures
orangefs_kill_sb(): deal with allocation failures
nfsd_umount(): deal with early sget() failures
nfs: avoid double-free on early sget() failures
jffs2_kill_sb(): deal with failed allocations
hypfs_kill_super(): deal with failed allocations
in https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git/log/?h=for-linus ,
I think the patch at
WARNING in kill_block_super
https://syzkaller.appspot.com/bug?id=588996a25a2587be2e3a54e8646728fb9cae44e7
is better.
next prev parent reply other threads:[~2018-04-10 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 8:21 syzbot
2018-04-02 23:00 ` Eric W. Biederman
2018-04-03 3:10 ` Eric Biggers
2018-04-03 10:45 ` Tetsuo Handa
2018-04-10 14:11 ` syzbot
2018-04-10 14:33 ` Tetsuo Handa [this message]
2018-04-21 10:43 ` Tetsuo Handa
2018-04-24 16:33 ` Eric W. Biederman
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=201804102333.BCC87582.MFHFOQFOOJLVtS@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=ebiggers3@gmail.com \
--cc=gs051095@gmail.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=riel@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=syzbot+7a1cff37dbbef9e7ba4c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@ZenIV.linux.org.uk \
--cc=wangkefeng.wang@huawei.com \
--subject='Re: KASAN: use-after-free Read in alloc_pid' \
/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
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).