From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Denys Vlasenko <dvlasenk@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
Sasha Levin <sasha.levin@oracle.com>,
Andi Kleen <ak@linux.intel.com>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [PATCH] arch/x86: fix out-of-bounds in get_wchan()
Date: Tue, 29 Sep 2015 20:41:41 +0200 [thread overview]
Message-ID: <20150929184141.GB18682@pd.tnic> (raw)
In-Reply-To: <CALCETrW5-_JFO_9F9bt2F1s5N_dseffYxCTX_SHJL39UcMyrFQ@mail.gmail.com>
On Tue, Sep 29, 2015 at 11:30:33AM -0700, Andy Lutomirski wrote:
> Also, I like Borislav's READ_ONCE suggestion. Let's avoid TOCTOU due
> to optimization.
Dmitry's original patch did READ_ONCE already.
> Re: a CVE: if anyone wants a CVE, ask oss-security. It's unclear to me
> exactly how one might exploit this.
I was just asking - it possibly leaking sensitive info and all.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2015-09-29 18:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 9:00 [PATCH] arch/x86: fix out-of-bounds in get_wchan() Dmitry Vyukov
2015-09-28 9:37 ` Borislav Petkov
2015-09-28 9:49 ` Dmitry Vyukov
2015-09-28 10:23 ` Borislav Petkov
2015-09-28 10:33 ` Dmitry Vyukov
2015-09-28 10:51 ` Borislav Petkov
2015-09-28 9:54 ` Dmitry Vyukov
2015-09-28 10:32 ` Borislav Petkov
2015-09-28 15:40 ` Andrey Ryabinin
2015-09-28 16:08 ` Dmitry Vyukov
2015-09-28 16:32 ` Thomas Gleixner
2015-09-29 18:15 ` Andy Lutomirski
2015-09-29 18:30 ` Andy Lutomirski
2015-09-29 18:41 ` Borislav Petkov [this message]
2015-09-30 7:15 ` [PATCH] fs/proc: Don't expose absolute kernel addresses via wchan Ingo Molnar
2015-09-30 7:35 ` Thomas Gleixner
2015-09-30 13:59 ` [PATCH v2] " Ingo Molnar
2015-09-30 20:36 ` Thomas Gleixner
2015-09-30 21:21 ` Kees Cook
2015-09-30 21:38 ` Thomas Gleixner
2015-10-01 7:57 ` [PATCH v3] fs/proc, core/debug: " Ingo Molnar
2015-10-01 8:57 ` Andrey Ryabinin
2015-10-01 9:29 ` Ingo Molnar
2015-10-01 10:16 ` Andrey Ryabinin
2015-10-01 10:39 ` Ingo Molnar
2015-10-01 10:47 ` Andrey Ryabinin
2015-10-01 10:57 ` [PATCH v5] " Ingo Molnar
2015-10-01 9:37 ` [PATCH v4] " Ingo Molnar
2015-10-01 12:49 ` [tip:core/debug] fs/proc, core/debug: Don' t " tip-bot for Ingo Molnar
2015-09-30 8:07 ` [PATCH] arch/x86: fix out-of-bounds in get_wchan() Thomas Gleixner
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=20150929184141.GB18682@pd.tnic \
--to=bp@alien8.de \
--cc=ak@linux.intel.com \
--cc=andreyknvl@google.com \
--cc=dvlasenk@redhat.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=kasan-dev@googlegroups.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=ryabinin.a.a@gmail.com \
--cc=sasha.levin@oracle.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).