On Fri, Aug 11, 2017 at 08:30:45AM -0700, Greg Kroah-Hartman wrote:
> On Fri, Aug 11, 2017 at 09:14:09AM +0200, Johannes Thumshirn wrote:
> > On Thu, Aug 10, 2017 at 08:11:34AM -0700, Greg KH wrote:
> > > else between it and the newer one? Drop this and you provide a
> > > backport? Something
On Fri, Aug 11, 2017 at 08:30:45AM -0700, Greg Kroah-Hartman wrote:
> On Fri, Aug 11, 2017 at 09:14:09AM +0200, Johannes Thumshirn wrote:
> > On Thu, Aug 10, 2017 at 08:11:34AM -0700, Greg KH wrote:
> > > else between it and the newer one? Drop this and you provide a
> > > backport? Something
On Fri, Aug 11, 2017 at 09:14:09AM +0200, Johannes Thumshirn wrote:
> On Thu, Aug 10, 2017 at 08:11:34AM -0700, Greg KH wrote:
> > else between it and the newer one? Drop this and you provide a
> > backport? Something else?
> >
> > Totally confusing...
>
> Sorry for confusing you, here's the
On Fri, Aug 11, 2017 at 09:14:09AM +0200, Johannes Thumshirn wrote:
> On Thu, Aug 10, 2017 at 08:11:34AM -0700, Greg KH wrote:
> > else between it and the newer one? Drop this and you provide a
> > backport? Something else?
> >
> > Totally confusing...
>
> Sorry for confusing you, here's the
On Thu, Aug 10, 2017 at 08:11:34AM -0700, Greg KH wrote:
> else between it and the newer one? Drop this and you provide a
> backport? Something else?
>
> Totally confusing...
Sorry for confusing you, here's the backport for your 4.12 stable branch,
Thanks,
Johannes
>From
On Thu, Aug 10, 2017 at 08:11:34AM -0700, Greg KH wrote:
> else between it and the newer one? Drop this and you provide a
> backport? Something else?
>
> Totally confusing...
Sorry for confusing you, here's the backport for your 4.12 stable branch,
Thanks,
Johannes
>From
On Thu, Aug 10, 2017 at 08:14:14AM +0200, Johannes Thumshirn wrote:
> On Wed, Aug 09, 2017 at 09:51:48AM -0700, Greg KH wrote:
> > 4.12-stable review patch. If anyone has any objections, please let me know.
>
> Yep I do, please don't use this one. It has a follow up/was superseded by:
>
On Thu, Aug 10, 2017 at 08:14:14AM +0200, Johannes Thumshirn wrote:
> On Wed, Aug 09, 2017 at 09:51:48AM -0700, Greg KH wrote:
> > 4.12-stable review patch. If anyone has any objections, please let me know.
>
> Yep I do, please don't use this one. It has a follow up/was superseded by:
>
On 09/08/17 17:51, Greg Kroah-Hartman wrote:
> 4.12-stable review patch. If anyone has any objections, please let me know.
>
> ---
I repeat my comments when the patch was queued for stable:
1. Johannes' commit message says that the transfer must have a length bigger
than 0, so the code
On 09/08/17 17:51, Greg Kroah-Hartman wrote:
> 4.12-stable review patch. If anyone has any objections, please let me know.
>
> ---
I repeat my comments when the patch was queued for stable:
1. Johannes' commit message says that the transfer must have a length bigger
than 0, so the code
On Wed, Aug 09, 2017 at 09:51:48AM -0700, Greg KH wrote:
> 4.12-stable review patch. If anyone has any objections, please let me know.
Yep I do, please don't use this one. It has a follow up/was superseded by:
f930c7043663 ("scsi: sg: only check for dxfer_len greater than 256M")
in Linus' tree
On Wed, Aug 09, 2017 at 09:51:48AM -0700, Greg KH wrote:
> 4.12-stable review patch. If anyone has any objections, please let me know.
Yep I do, please don't use this one. It has a follow up/was superseded by:
f930c7043663 ("scsi: sg: only check for dxfer_len greater than 256M")
in Linus' tree
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Thumshirn
commit 68c59fcea1f2c6a54c62aa896cc623c1b5bc9b47 upstream.
SG_DXFER_FROM_DEV transfers do not necessarily have a dxferp as we set
it to NULL for the old
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Thumshirn
commit 68c59fcea1f2c6a54c62aa896cc623c1b5bc9b47 upstream.
SG_DXFER_FROM_DEV transfers do not necessarily have a dxferp as we set
it to NULL for the old sg_io read/write
14 matches
Mail list logo