From: Joey Pabalinas <joeypabalinas@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"Wanpeng Li" <kernellwp@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
dledford@redhat.com, "KVM list" <kvm@vger.kernel.org>,
"Radim Krčmář" <rkrcmar@redhat.com>, "Wei Wu" <ww9210@gmail.com>,
"Kostya Serebryany" <kcc@google.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
syzkaller <syzkaller@googlegroups.com>,
"Dan Williams" <dan.j.williams@intel.com>,
"Chris Mason" <clm@fb.com>, "Jonathan Corbet" <corbet@lwn.net>,
"Kees Cook" <keescook@google.com>,
"Laura Abbott" <labbott@redhat.com>,
"Olof Johansson" <olofj@google.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Theodore Tso" <tytso@google.com>,
Tim.Bird@sony.com, "Joey Pabalinas" <joeypabalinas@gmail.com>
Subject: Re: [PATCH] KVM: X86: Fix scan ioapic use-before-initialization
Date: Fri, 28 Dec 2018 12:13:08 -1000 [thread overview]
Message-ID: <20181228221308.ev2mjvnh273qcrml@gmail.com> (raw)
In-Reply-To: <CACT4Y+YRs3HLf7-0AhMPMuvHGvKHge_7R5Qo6Q9H1A2w1fQ39A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On Fri, Dec 28, 2018 at 10:43:11AM +0100, 'Dmitry Vyukov' via syzkaller wrote:
> On Thu, Dec 27, 2018 at 6:00 PM Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > Nobody reads the kernel mailing list directly - there's just too much traffic.
>
> As the result bug reports and patches got lots and this is bad and it
> would be useful to stop it from happening and there are known ways for
> this.
What are the "known ways"? The only effective way I can think of is to
setup personal email filters for specific topics, and while this is
useful and something I do myself, it requires a lot of up front work.
I don't think it's realistic to expect others to be doing this
instead of just subscribing to the topic lists.
--
Cheers,
Joey Pabalinas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-28 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 8:34 [PATCH] KVM: X86: Fix scan ioapic use-before-initialization Wanpeng Li
2018-11-25 17:31 ` Paolo Bonzini
2018-12-27 14:28 ` Dmitry Vyukov
2018-12-27 16:59 ` Linus Torvalds
2018-12-28 9:43 ` Dmitry Vyukov
2018-12-28 21:08 ` Linus Torvalds
2019-01-02 14:08 ` Dmitry Vyukov
2019-01-09 8:28 ` Dmitry Vyukov
2018-12-28 22:13 ` Joey Pabalinas [this message]
2019-01-02 13:43 ` Dmitry Vyukov
2019-01-07 23:11 ` Paolo Bonzini
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=20181228221308.ev2mjvnh273qcrml@gmail.com \
--to=joeypabalinas@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=clm@fb.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=daniel@ffwll.ch \
--cc=dledford@redhat.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kcc@google.com \
--cc=keescook@google.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olofj@google.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=rostedt@goodmis.org \
--cc=syzkaller@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@google.com \
--cc=ww9210@gmail.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;
as well as URLs for NNTP newsgroup(s).