From: Linus Torvalds <torvalds@linux-foundation.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Eric Biggers" <ebiggers@kernel.org>,
"KVM list" <kvm@vger.kernel.org>,
syzbot <syzbot+7857962b4d45e602b8ad@syzkaller.appspotmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"Tetsuo Handa" <penguin-kernel@i-love.sakura.ne.jp>,
syzkaller-bugs@googlegroups.com,
"Al Viro" <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] kvm: properly check debugfs dentry before using it
Date: Thu, 28 Feb 2019 08:58:30 -0800 [thread overview]
Message-ID: <CAHk-=wgs59YJY+OPEPoORU-osNDyOsPo1bbJ8=14=ZTNHn11OA@mail.gmail.com> (raw)
In-Reply-To: <20190228153437.GI8481@kroah.com>
On Thu, Feb 28, 2019 at 7:34 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> Linus, this should go in before 5.0-final is out, as it resolves a
> problem found by syzbot. Paolo has given his ack for me to send this
> directly to you. If you want this in [GIT PULL] format, I can do that
> as well.
Applied, thanks,
Linus
next prev parent reply other threads:[~2019-02-28 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 15:34 [PATCH] kvm: properly check debugfs dentry before using it Greg Kroah-Hartman
2019-02-28 16:58 ` Linus Torvalds [this message]
2019-02-28 17:17 ` Eric Biggers
2019-02-28 18:04 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2019-01-30 10:35 general protection fault in __dentry_path syzbot
2019-02-21 4:14 ` syzbot
2019-02-26 19:19 ` Eric Biggers
2019-02-28 15:08 ` [PATCH] kvm: properly check debugfs dentry before using it Greg Kroah-Hartman
2019-02-28 15:14 ` Paolo Bonzini
2019-02-28 15:32 ` Greg Kroah-Hartman
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='CAHk-=wgs59YJY+OPEPoORU-osNDyOsPo1bbJ8=14=ZTNHn11OA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=ebiggers@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rkrcmar@redhat.com \
--cc=syzbot+7857962b4d45e602b8ad@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 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).