public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Isaac Manjarres <isaacmanjarres@google.com>
To: Mark Brown <broonie@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	Saravana Kannan <saravanak@google.com>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Aidan MacDonald <aidanmacdonald.0x0@gmail.com>,
	Amit Pundir <amit.pundir@linaro.org>,
	John Stultz <jstultz@google.com>,
	stable@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>,
	kernel-team@android.com,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] regmap-irq: Fix out-of-bounds access when allocating config buffers
Date: Tue, 11 Jul 2023 15:11:22 -0700	[thread overview]
Message-ID: <ZK3TiuPZr0A8iaNN@google.com> (raw)
In-Reply-To: <8e5fba54-9ec7-45a7-8dd6-6ea63d853907@sirena.org.uk>

On Tue, Jul 11, 2023 at 08:50:08PM +0100, Mark Brown wrote:
> On Tue, Jul 11, 2023 at 12:30:58PM -0700, Isaac J. Manjarres wrote:
> 
> > [   14.033877][    T1] ==================================================================
> > [   14.042507][    T1] BUG: KASAN: invalid-access in regmap_add_irq_chip_fwnode+0x594/0x1364
> > [   14.050796][    T1] Write of size 8 at addr 06ffff8081021850 by task init/1
> > [   14.057841][    T1] Pointer tag: [06], memory tag: [fe]
> > [   14.063124][    T1]
> > [   14.065349][    T1] CPU: 2 PID: 1 Comm: init Tainted: G        W   E      6.4.0-mainline-g6a4b67fef3e2 #1
> > [   14.075014][    T1] Hardware name: Thundercomm Dragonboard 845c (DT)
> > [   14.081432][    T1] Call trace:
> 
> 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.

Hi Mark,

Thanks for your feedback. I'll go ahead and send out a new version of
the patch with a trimmed down commit message.

Thanks,
Isaac

  reply	other threads:[~2023-07-11 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 19:30 [PATCH v1] regmap-irq: Fix out-of-bounds access when allocating config buffers Isaac J. Manjarres
2023-07-11 19:50 ` Mark Brown
2023-07-11 22:11   ` Isaac Manjarres [this message]
2023-07-11 22:24     ` Mark Brown
2023-07-11 22:31       ` Isaac Manjarres
2023-07-12  4:54 ` Amit Pundir
2023-07-12 22:06 ` Mark Brown

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=ZK3TiuPZr0A8iaNN@google.com \
    --to=isaacmanjarres@google.com \
    --cc=aidanmacdonald.0x0@gmail.com \
    --cc=amit.pundir@linaro.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jstultz@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=rafael@kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=saravanak@google.com \
    --cc=stable@vger.kernel.org \
    --cc=tomeu.vizoso@collabora.com \
    --cc=ulf.hansson@linaro.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