All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Kees Cook <keescook@chromium.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Omar Sandoval <osandov@fb.com>,
	syzbot <syzbot+b382ba6a802a3d242790@syzkaller.appspotmail.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Al Viro <viro@zeniv.linux.org.uk>, Jens Axboe <axboe@fb.com>
Subject: Re: BUG: unable to handle kernel paging request in dput (2)
Date: Thu, 31 Jan 2019 19:18:45 +0900	[thread overview]
Message-ID: <511b89e2-9c0d-c4a2-de27-e803bc20c38c@i-love.sakura.ne.jp> (raw)
In-Reply-To: <CAGXu5jKezbEYNUEhMZi=4UhKV9m8wiJc1fo+fxNf5CaaBUMP8w@mail.gmail.com>

On 2019/01/31 19:09, Kees Cook wrote:
> FYI, this patch does not fix the relay.c crash I bisected... I think
> more clean-up is needed?

You mean "general protection fault in relay_open_buf" at
https://syzkaller.appspot.com/bug?id=080fbc3a5d10bd8ada100799168ebe1b70e2eefa ?

  reply	other threads:[~2019-01-31 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 10:35 BUG: unable to handle kernel paging request in dput (2) syzbot
2019-01-30 11:11 ` Tetsuo Handa
2019-01-30 11:23   ` Greg Kroah-Hartman
2019-01-30 11:26   ` Tetsuo Handa
2019-01-30 11:34     ` Greg Kroah-Hartman
2019-01-30 11:40     ` Greg Kroah-Hartman
2019-01-31 10:09       ` Kees Cook
2019-01-31 10:18         ` Tetsuo Handa [this message]
2019-01-31 10:53         ` Greg Kroah-Hartman
2019-01-30 11:20 ` syzbot

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=511b89e2-9c0d-c4a2-de27-e803bc20c38c@i-love.sakura.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=axboe@fb.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osandov@fb.com \
    --cc=syzbot+b382ba6a802a3d242790@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --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 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.