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] [day] [month] [year] [list]
Date:   Wed, 26 Apr 2017 10:17:05 -0700 (PDT)
From:   Stefano Stabellini <sstabellini@...nel.org>
To:     Catalin Marinas <catalin.marinas@....com>
cc:     Stefano Stabellini <sstabellini@...nel.org>, jgross@...e.com,
        will.deacon@....com, linux-kernel@...r.kernel.org,
        linux@...linux.org.uk, Julien Grall <julien.grall@....com>,
        boris.ostrovsky@...cle.com, xen-devel@...ts.xen.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/2] xen/arm, arm64: fix xen_dma_ops after 815dd18
 "Consolidate get_dma_ops..."

On Wed, 26 Apr 2017, Catalin Marinas wrote:
> On Wed, Apr 26, 2017 at 10:00:30AM -0700, Stefano Stabellini wrote:
> > On Wed, 26 Apr 2017, Catalin Marinas wrote:
> > > On Tue, Apr 25, 2017 at 10:22:00AM -0700, Stefano Stabellini wrote:
> > > > On Tue, 25 Apr 2017, Julien Grall wrote:
> > > > > On 24/04/17 20:16, Stefano Stabellini wrote:
> > > > > > Given the outstanding regression we need to fix as soon as possible,
> > > > > > I'll queue these patches on the xentip tree for 4.12.
> > > > > 
> > > > > It looks like there is another rc for 4.11. I am wondering whether you could
> > > > > try to send a pull request to Linus so it can be fixed in 4.11?
> > > > 
> > > > No, especially without input from Russell.
> > > 
> > > You could add a "Fixes" tag to the first patch so that it gets
> > > back-ported to 4.11.x once it hits mainline (the second patch is just
> > > cosmetic):
> > > 
> > > Fixes: 815dd18788fe ("treewide: Consolidate get_dma_ops() implementations")
> > 
> > I did add:
> > 
> >   Cc: <stable@...r.kernel.org>        [4.11+]
> > 
> > I thought that would be enough to trigger a backport?
> 
> Either would do. I didn't see it in the patch you posted, that's why I
> mentioned it.

Thanks, I appreciated it!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ