linux-kernel - Re: Backport of spi-fsl-spi bugfix to 3.14.y

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: <20150125173853.GA6467@kroah.com>
Date:	Sun, 25 Jan 2015 09:38:53 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Esben Haabendal <esben.haabendal@...il.com>,
	stable@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-spi@...r.kernel.org, Stefan Roese <sr@...x.de>
Subject: Re: Backport of spi-fsl-spi bugfix to 3.14.y

On Fri, Jan 23, 2015 at 12:45:29PM +0000, Mark Brown wrote:
> On Tue, Jan 06, 2015 at 10:15:47PM +0100, Esben Haabendal wrote:
> > On 5 January 2015 at 16:48, Mark Brown <broonie@...nel.org> wrote:
> 
> > >> Please consider commit 4302a59629f7a0bd70fd1605d2b558597517372a
> > >> (spi: fsl: Fix problem with multi message transfers) for inclusion in
> > >> stable kernel 3.14.
> 
> > >> It fixes a regression when using mmc_spi driver on top of spi-fsl-spi
> > >> driver (tested with powerpc mpc8313 based board).
> 
> > > Has this ever worked?
> 
> > Yes, I have used mmc_spi with spi-fsl-spi on the same board with success
> > with in 2.6.33, 3.0 and 3.4.
> 
> > I have no idea what has caused this to break.  Maybe mmc_spi driver was
> > not doing multi message transfers earlier?
> 
> So, I now see this has actually been merged into stable without getting
> to the bottom of why it's helping anything...  this is a bit worrying
> since it's adding new functionality and not really a bug fix.  It'd have
> been good to at least get a followup here.

Do you want me to revert something from the stable tree?  If so, has it
also been reverted upstream?

confused,

greg k-h
--
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/