linux-kernel - Re: [PATCH 3/5] Blackfin SPI Driver: fix NULL pointer crash

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a0902051429q2b76c7b7nf4187178b73f979@mail.gmail.com>
Date:	Thu, 5 Feb 2009 17:29:18 -0500
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Bryan Wu <cooloney@...nel.org>, dbrownell@...rs.sourceforge.net,
	spi-devel-general@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/5] Blackfin SPI Driver: fix NULL pointer crash

On Thu, Feb 5, 2009 at 17:12, Andrew Morton wrote:
> On Thu,  5 Feb 2009 18:07:31 +0800 Bryan Wu wrote:
>> From: Mike Frysinger <vapier.adi@...il.com>
>> fix NULL pointer crash when cleaning up from invalid platform resources
>>
>> Signed-off-by: Mike Frysinger <vapier.adi@...il.com>
>> Signed-off-by: Bryan Wu <cooloney@...nel.org>
>> ---
>>  drivers/spi/spi_bfin5xx.c |    3 +++
>>  1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/spi/spi_bfin5xx.c b/drivers/spi/spi_bfin5xx.c
>> index ce24d5e..b6098b5 100644
>> --- a/drivers/spi/spi_bfin5xx.c
>> +++ b/drivers/spi/spi_bfin5xx.c
>> @@ -1240,6 +1240,9 @@ static void bfin_spi_cleanup(struct spi_device *spi)
>>  {
>>       struct chip_data *chip = spi_get_ctldata(spi);
>>
>> +     if (!chip)
>> +             return;
>> +
>>       if ((chip->chip_select_num > 0)
>>               && (chip->chip_select_num <= spi->master->num_chipselect))
>>               peripheral_free(ssel[spi->master->bus_num]
>
> This one looks like 2.6.29 material to me.
>
> If you believe that it should be backported to earlier kernels then
> please let me know.  indicating whcih kernel versions would help things
> a bit, too.

including with 2.6.29 would be a good thing ... we havent quite synced
up our development process enough yet to do that kind of tracking, so
all of our stuff just goes into "the next thing" ...
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/