All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Gabor Juhos <j4g8y7@gmail.com>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	 Mark Brown <broonie@kernel.org>,
	 Md Sadre Alam <quic_mdalam@quicinc.com>,
	Varadarajan Narayanan <quic_varada@quicinc.com>,
	 Sricharan Ramabadhran <quic_srichara@quicinc.com>,
	 Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	 linux-spi@vger.kernel.org, linux-mtd@lists.infradead.org,
	 linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Lakshmi Sowjanya D <quic_laksd@quicinc.com>
Subject: Re: [PATCH v2 2/2] mtd: nand: qpic_common: prevent out of bounds access of BAM arrays
Date: Mon, 02 Jun 2025 15:54:09 +0200	[thread overview]
Message-ID: <87a56qp7um.fsf@bootlin.com> (raw)
In-Reply-To: <28db650d-a911-4df9-9ad4-f926ea0683e6@gmail.com> (Gabor Juhos's message of "Fri, 30 May 2025 13:07:35 +0200")


On 30/05/2025 at 13:07:35 +02, Gabor Juhos <j4g8y7@gmail.com> wrote:

> 2025. 05. 30. 10:56 keltezéssel, Bryan O'Donoghue írta:
>
> ...
>
>> This one doesn't apply to -next
>
> It is because the series is based on the SPI tree, and -next contains another
> change for 'drivers/mtd/nand/qpic_common.c' which comes from the MTD tree.
>
> It can be applied by specifying the 'M' switch for b4 shazam.

I suggest you rebase on -rc1 (when it's out) and resend to simplify
Mark's life.

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Gabor Juhos <j4g8y7@gmail.com>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	 Mark Brown <broonie@kernel.org>,
	 Md Sadre Alam <quic_mdalam@quicinc.com>,
	Varadarajan Narayanan <quic_varada@quicinc.com>,
	 Sricharan Ramabadhran <quic_srichara@quicinc.com>,
	 Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	 linux-spi@vger.kernel.org, linux-mtd@lists.infradead.org,
	 linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Lakshmi Sowjanya D <quic_laksd@quicinc.com>
Subject: Re: [PATCH v2 2/2] mtd: nand: qpic_common: prevent out of bounds access of BAM arrays
Date: Mon, 02 Jun 2025 15:54:09 +0200	[thread overview]
Message-ID: <87a56qp7um.fsf@bootlin.com> (raw)
In-Reply-To: <28db650d-a911-4df9-9ad4-f926ea0683e6@gmail.com> (Gabor Juhos's message of "Fri, 30 May 2025 13:07:35 +0200")


On 30/05/2025 at 13:07:35 +02, Gabor Juhos <j4g8y7@gmail.com> wrote:

> 2025. 05. 30. 10:56 keltezéssel, Bryan O'Donoghue írta:
>
> ...
>
>> This one doesn't apply to -next
>
> It is because the series is based on the SPI tree, and -next contains another
> change for 'drivers/mtd/nand/qpic_common.c' which comes from the MTD tree.
>
> It can be applied by specifying the 'M' switch for b4 shazam.

I suggest you rebase on -rc1 (when it's out) and resend to simplify
Mark's life.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2025-06-02 13:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 17:25 [PATCH v2 0/2] spi: spi-qpic-snand: avoid memory corruption Gabor Juhos
2025-05-29 17:25 ` Gabor Juhos
2025-05-29 17:25 ` [PATCH v2 1/2] spi: spi-qpic-snand: reallocate BAM transactions Gabor Juhos
2025-05-29 17:25   ` Gabor Juhos
2025-05-29 17:25 ` [PATCH v2 2/2] mtd: nand: qpic_common: prevent out of bounds access of BAM arrays Gabor Juhos
2025-05-29 17:25   ` Gabor Juhos
2025-05-30  8:56   ` Bryan O'Donoghue
2025-05-30  8:56     ` Bryan O'Donoghue
2025-05-30 11:07     ` Gabor Juhos
2025-05-30 11:07       ` Gabor Juhos
2025-06-02 13:54       ` Miquel Raynal [this message]
2025-06-02 13:54         ` Miquel Raynal
2025-06-03  9:16         ` Gabor Juhos
2025-06-03  9:16           ` Gabor Juhos
2025-06-02 13:53   ` Miquel Raynal
2025-06-02 13:53     ` Miquel Raynal

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=87a56qp7um.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=j4g8y7@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=quic_laksd@quicinc.com \
    --cc=quic_mdalam@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=quic_varada@quicinc.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    /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.