All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Joe Burmeister <joe.burmeister@devtank.co.uk>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	bcm-kernel-feedback-list@broadcom.com,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	linux-spi@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: bcm2835: Fix buffer overflow with CS able to go beyond limit.
Date: Thu, 22 Apr 2021 17:42:23 +0100	[thread overview]
Message-ID: <20210422164223.GA36209@sirena.org.uk> (raw)
In-Reply-To: <20210420083402.6950-1-joe.burmeister@devtank.co.uk>

[-- Attachment #1: Type: text/plain, Size: 468 bytes --]

On Tue, Apr 20, 2021 at 09:34:02AM +0100, Joe Burmeister wrote:
> It was previoulsy possible to have a device tree with more chips than
> the driver supports and go off the end of CS arrays.
> 
> This patches inforces CS limit but sets that limit to the max of the
> default limit and what is in the device tree when driver is loaded.

This doesn't apply against current code, please check and resend.

Also s/previoulsy/previously/ and s/inforces/enforces/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Joe Burmeister <joe.burmeister@devtank.co.uk>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	bcm-kernel-feedback-list@broadcom.com,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	linux-spi@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: bcm2835: Fix buffer overflow with CS able to go beyond limit.
Date: Thu, 22 Apr 2021 17:42:23 +0100	[thread overview]
Message-ID: <20210422164223.GA36209@sirena.org.uk> (raw)
In-Reply-To: <20210420083402.6950-1-joe.burmeister@devtank.co.uk>


[-- Attachment #1.1: Type: text/plain, Size: 468 bytes --]

On Tue, Apr 20, 2021 at 09:34:02AM +0100, Joe Burmeister wrote:
> It was previoulsy possible to have a device tree with more chips than
> the driver supports and go off the end of CS arrays.
> 
> This patches inforces CS limit but sets that limit to the max of the
> default limit and what is in the device tree when driver is loaded.

This doesn't apply against current code, please check and resend.

Also s/previoulsy/previously/ and s/inforces/enforces/

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-04-22 16:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  8:34 [PATCH] spi: bcm2835: Fix buffer overflow with CS able to go beyond limit Joe Burmeister
2021-04-20  8:34 ` Joe Burmeister
2021-04-22 16:42 ` Mark Brown [this message]
2021-04-22 16:42   ` Mark Brown
2021-04-22 16:50 ` Florian Fainelli
2021-04-22 16:50   ` Florian Fainelli
2021-04-22 20:10   ` Joe Burmeister
2021-04-22 20:10     ` Joe Burmeister
2021-04-22 23:49     ` Florian Fainelli
2021-04-22 23:49       ` Florian Fainelli
2021-04-23 10:03       ` Joe Burmeister
2021-04-23 10:03         ` Joe Burmeister
2021-04-23 11:57         ` Mark Brown
2021-04-23 11:57           ` Mark Brown
2021-04-23 14:12           ` Joe Burmeister
2021-04-23 14:12             ` Joe Burmeister
2021-04-23 16:20             ` Mark Brown
2021-04-23 16:20               ` Mark Brown
2021-04-23 17:34               ` Nicolas Saenz Julienne
2021-04-23 17:34                 ` Nicolas Saenz Julienne
2021-05-01 19:51               ` Lukas Wunner
2021-05-04 11:51                 ` Mark Brown
2021-05-04 11:51                   ` Mark Brown
2021-05-04 13:53                   ` Lukas Wunner

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=20210422164223.GA36209@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=joe.burmeister@devtank.co.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.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.