Request for adding patches to stable tree

Request for adding patches to stable tree

[Juergen Gross]

I've seen reports for crashes under Xen on EFI machines with dom0
running kernel 4.12. Reason seem to be missing upstream patches
6c64447ec58b0bac612732303f7ab04562124587 ("x86/xen/efi: Initialize only
the EFI struct members used by Xen") and
457ea3f7e97881f937136ce0ba1f29f82b9abdb0 ("efi: Process the MEMATTR
table only if EFI_MEMMAP is enabled")

Please consider adding those patches to (at least) the stable 4.12 tree.


Thanks,

Juergen

Re: Request for adding patches to stable tree

[Greg KH]

On Tue, Jul 18, 2017 at 03:30:05PM +0200, Juergen Gross wrote:
> I've seen reports for crashes under Xen on EFI machines with dom0
> running kernel 4.12. Reason seem to be missing upstream patches
> 6c64447ec58b0bac612732303f7ab04562124587 ("x86/xen/efi: Initialize only
> the EFI struct members used by Xen") and
> 457ea3f7e97881f937136ce0ba1f29f82b9abdb0 ("efi: Process the MEMATTR
> table only if EFI_MEMMAP is enabled")
> 
> Please consider adding those patches to (at least) the stable 4.12 tree.

Both of these are already queued up.  Usually if they are marked with a
"stable@" tag on the patch, I will pick it up automatically.

thanks,

greg k-h

Re: Request for adding patches to stable tree

[Daniel Kiper]

On Tue, Jul 18, 2017 at 05:45:11PM +0200, Greg KH wrote:
> On Tue, Jul 18, 2017 at 03:30:05PM +0200, Juergen Gross wrote:
> > I've seen reports for crashes under Xen on EFI machines with dom0
> > running kernel 4.12. Reason seem to be missing upstream patches
> > 6c64447ec58b0bac612732303f7ab04562124587 ("x86/xen/efi: Initialize only
> > the EFI struct members used by Xen") and
> > 457ea3f7e97881f937136ce0ba1f29f82b9abdb0 ("efi: Process the MEMATTR
> > table only if EFI_MEMMAP is enabled")
> >
> > Please consider adding those patches to (at least) the stable 4.12 tree.
>
> Both of these are already queued up.  Usually if they are marked with a
> "stable@" tag on the patch, I will pick it up automatically.

I am not sure what do you mean by ""stable@" tag on the patch". Could you clarify?

Daniel

Re: Request for adding patches to stable tree

[Greg KH]

On Wed, Jul 19, 2017 at 01:31:11PM +0200, Daniel Kiper wrote:
> On Tue, Jul 18, 2017 at 05:45:11PM +0200, Greg KH wrote:
> > On Tue, Jul 18, 2017 at 03:30:05PM +0200, Juergen Gross wrote:
> > > I've seen reports for crashes under Xen on EFI machines with dom0
> > > running kernel 4.12. Reason seem to be missing upstream patches
> > > 6c64447ec58b0bac612732303f7ab04562124587 ("x86/xen/efi: Initialize only
> > > the EFI struct members used by Xen") and
> > > 457ea3f7e97881f937136ce0ba1f29f82b9abdb0 ("efi: Process the MEMATTR
> > > table only if EFI_MEMMAP is enabled")
> > >
> > > Please consider adding those patches to (at least) the stable 4.12 tree.
> >
> > Both of these are already queued up.  Usually if they are marked with a
> > "stable@" tag on the patch, I will pick it up automatically.
> 
> I am not sure what do you mean by ""stable@" tag on the patch". Could you clarify?

Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

Sometimes I wonder why we even write documentation...

Re: Request for adding patches to stable tree

[Daniel Kiper]

On Wed, Jul 19, 2017 at 01:37:12PM +0200, Greg KH wrote:
> On Wed, Jul 19, 2017 at 01:31:11PM +0200, Daniel Kiper wrote:
> > On Tue, Jul 18, 2017 at 05:45:11PM +0200, Greg KH wrote:
> > > On Tue, Jul 18, 2017 at 03:30:05PM +0200, Juergen Gross wrote:
> > > > I've seen reports for crashes under Xen on EFI machines with dom0
> > > > running kernel 4.12. Reason seem to be missing upstream patches
> > > > 6c64447ec58b0bac612732303f7ab04562124587 ("x86/xen/efi: Initialize only
> > > > the EFI struct members used by Xen") and
> > > > 457ea3f7e97881f937136ce0ba1f29f82b9abdb0 ("efi: Process the MEMATTR
> > > > table only if EFI_MEMMAP is enabled")
> > > >
> > > > Please consider adding those patches to (at least) the stable 4.12 tree.
> > >
> > > Both of these are already queued up.  Usually if they are marked with a
> > > "stable@" tag on the patch, I will pick it up automatically.
> >
> > I am not sure what do you mean by ""stable@" tag on the patch". Could you clarify?
>
> Please read:
>     https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

Ahhh... You mean "CC: ..." in the patch commit message. I CCed "stable@" from
"git send-email" command line and that it is why it did not work.

> Sometimes I wonder why we even write documentation...

Next time I will take a look at that doc.

Thanks,

Daniel