[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZK3YXpzlxhwMGiuj@google.com>
Date: Tue, 11 Jul 2023 15:31:58 -0700
From: Isaac Manjarres <isaacmanjarres@...gle.com>
To: Mark Brown <broonie@...nel.org>
Cc: Russell King <linux@...linux.org.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
"Russell King (Oracle)" <rmk+kernel@...linux.org.uk>,
Saravana Kannan <saravanak@...gle.com>,
Tomeu Vizoso <tomeu.vizoso@...labora.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Aidan MacDonald <aidanmacdonald.0x0@...il.com>,
Amit Pundir <amit.pundir@...aro.org>,
John Stultz <jstultz@...gle.com>, stable@...r.kernel.org,
Catalin Marinas <catalin.marinas@....com>,
kernel-team@...roid.com,
Russell King <rmk+kernel@....linux.org.uk>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] regmap-irq: Fix out-of-bounds access when allocating
config buffers
On Tue, Jul 11, 2023 at 11:24:59PM +0100, Mark Brown wrote:
> On Tue, Jul 11, 2023 at 03:11:22PM -0700, Isaac Manjarres wrote:
> > On Tue, Jul 11, 2023 at 08:50:08PM +0100, Mark Brown wrote:
>
> > > Please think hard before including complete backtraces in upstream
> > > reports, they are very large and contain almost no useful information
> > > relative to their size so often obscure the relevant content in your
> > > message. If part of the backtrace is usefully illustrative (it often is
> > > for search engines if nothing else) then it's usually better to pull out
> > > the relevant sections.
>
> > Thanks for your feedback. I'll go ahead and send out a new version of
> > the patch with a trimmed down commit message.
>
> It's OK, I did some local edits myself.
Thanks Mark!
--Isaac
Powered by blists - more mailing lists