From: syzbot <syzbot+16c3a70e1e9b29346c43@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dvyukov@google.com,
ebiggers@google.com, gregkh@linuxfoundation.org,
jrdr.linux@gmail.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, rientjes@google.com,
syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in relay_open_buf
Date: Thu, 31 Jan 2019 03:35:03 -0800 [thread overview]
Message-ID: <000000000000d671490580bf6a53@google.com> (raw)
In-Reply-To: <CACT4Y+ZtG6Ef4vRApPuZsG0pquCV94Hg0KYBxpgpQueaG8STHA@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+16c3a70e1e9b29346c43@syzkaller.appspotmail.com
Tested on:
commit: af0c9af1b3f6 fs/dcache: Track & report number of negative ..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3495238483eab50f
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=166d48df400000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2019-01-31 11:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 18:53 general protection fault in relay_open_buf syzbot
2019-01-31 9:54 ` Kees Cook
2019-01-31 10:44 ` Greg KH
2019-01-31 10:51 ` Greg KH
2019-01-31 11:16 ` Dmitry Vyukov
2019-01-31 11:22 ` Greg KH
2019-01-31 11:28 ` Dmitry Vyukov
2019-01-31 11:53 ` syzbot
2019-01-31 11:35 ` syzbot [this message]
2019-01-31 11:29 ` Tetsuo Handa
2019-01-31 11:54 ` Greg KH
2019-01-31 18:31 ` Kees Cook
2019-01-31 18:46 ` Greg KH
2019-02-01 3:57 ` Al Viro
2019-02-01 9:07 ` Greg KH
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=000000000000d671490580bf6a53@google.com \
--to=syzbot+16c3a70e1e9b29346c43@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=ebiggers@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jrdr.linux@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox