[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190115155532.GB6903@1wt.eu>
Date: Tue, 15 Jan 2019 16:55:32 +0100
From: Willy Tarreau <w@....eu>
To: Mark Brown <broonie@...nel.org>
Cc: Silvio Cesare <silvio.cesare@...il.com>,
linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
Dan Carpenter <dan.carpenter@...cle.com>,
Kees Cook <keescook@...omium.org>,
Will Deacon <will.deacon@....com>, Greg KH <greg@...ah.com>
Subject: Re: [PATCH 7/8] ASoC: dapm: change snprintf to scnprintf for
possible overflow
On Tue, Jan 15, 2019 at 03:44:36PM +0000, Mark Brown wrote:
> On Tue, Jan 15, 2019 at 04:16:15AM +0100, Willy Tarreau wrote:
> > On Mon, Jan 14, 2019 at 02:56:50PM +0000, Mark Brown wrote:
> > > On Sat, Jan 12, 2019 at 04:28:43PM +0100, Willy Tarreau wrote:
>
> > > I don't have a cover letter or anything before this in the series.
> > > What's going on with dependencies here?
>
> > Sorry for the lack of more context, I was just involved in putting a
> > subject line on each patch and passing them through get_maintainers.pl.
> > These ones were sent to the security list after this article was published:
>
> > http://blog.infosectcbr.com.au/2018/11/memory-bugs-in-multiple-linux-kernel.html
>
> So just to confirm it looks like these are just isolated projects with
> no interdepencies?
That's it : just a series of patches for the same bug in multiple drivers.
Now with your question I understand the confusion, it's caused by me sending
all of them as a single series. I should have sent them individually. My bad.
Regards,
Willy
Powered by blists - more mailing lists