From: Greg KH <gregkh@linuxfoundation.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Jiri Slaby <jslaby@suse.com>,
Or Cohen <orcohen@paloaltonetworks.com>,
textshell@uchuujin.de, Daniel Vetter <daniel.vetter@ffwll.ch>,
sam@ravnborg.org, mpatocka@redhat.com, ghalat@redhat.com,
linux-kernel@vger.kernel.org, jwilk@jwilk.net,
Nadav Markus <nmarkus@paloaltonetworks.com>,
syzkaller@googlegroups.com
Subject: Re: Bug report - slab-out-of-bounds in vcs_scr_readw
Date: Wed, 27 Nov 2019 17:30:30 +0100 [thread overview]
Message-ID: <20191127163030.GA3086596@kroah.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1911271121200.8537@knanqh.ubzr>
On Wed, Nov 27, 2019 at 11:24:52AM -0500, Nicolas Pitre wrote:
> On Wed, 27 Nov 2019, Greg KH wrote:
>
> > On Tue, Nov 26, 2019 at 04:55:32PM -0500, Nicolas Pitre wrote:
> > > Greg, could you apply this please?
> >
> > Yes, I will, but I don't seem to have it in my email archives anywhere,
> > was it burried in that long thread?
>
> I've seen much longer threads than this one, but yes it was at its tail.
> Hence the direct ping.
Yeah, I dug it out, sorry about that, my fault. All now queued up.
greg k-h
prev parent reply other threads:[~2019-11-27 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM6JnLeEnvjjQPyLeh+8dt5wGNud_vks5k_eXJZy2T1H7ao=hQ@mail.gmail.com>
2019-11-04 15:24 ` Bug report - slab-out-of-bounds in vcs_scr_readw Greg KH
2019-11-04 15:50 ` Nicolas Pitre
2019-11-04 16:15 ` Or Cohen
2019-11-04 18:33 ` Nicolas Pitre
2019-11-05 6:54 ` Jiri Slaby
2019-11-05 9:03 ` Or Cohen
2019-11-05 9:14 ` Jiri Slaby
2019-11-05 9:33 ` Nicolas Pitre
2019-11-05 10:29 ` Jiri Slaby
2019-11-05 10:53 ` Dmitry Vyukov
2019-11-05 13:44 ` Nicolas Pitre
2019-11-06 17:01 ` Or Cohen
2019-11-26 21:55 ` Nicolas Pitre
2019-11-27 6:45 ` Greg KH
2019-11-27 16:24 ` Nicolas Pitre
2019-11-27 16:30 ` Greg KH [this message]
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=20191127163030.GA3086596@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=ghalat@redhat.com \
--cc=jslaby@suse.com \
--cc=jwilk@jwilk.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=nico@fluxnic.net \
--cc=nmarkus@paloaltonetworks.com \
--cc=orcohen@paloaltonetworks.com \
--cc=sam@ravnborg.org \
--cc=syzkaller@googlegroups.com \
--cc=textshell@uchuujin.de \
/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.