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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190308123655.GA13818@kroah.com>
Date:   Fri, 8 Mar 2019 13:36:55 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
Cc:     stable@...r.kernel.org, Sasha Levin <sashal@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Jan Kiszka <jan.kiszka@...mens.com>,
        Jackie Liu <liuyun01@...inos.cn>,
        Kieran Bingham <kbingham@...nel.org>,
        Felipe Balbi <felipe.balbi@...ux.intel.com>,
        Dan Robertson <danlrobertson89@...il.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Kieran Bingham <kieran.bingham@...asonboard.com>
Subject: Re: [PATCH v3] scripts/gdb: replace flags (MS_xyz -> SB_xyz)

On Tue, Mar 05, 2019 at 01:47:58PM -0800, Nick Desaulniers wrote:
> On Tue, Mar 5, 2019 at 2:30 AM Kieran Bingham
> <kieran.bingham@...asonboard.com> wrote:
> >
> > From: Jackie Liu <liuyun01@...inos.cn>
> >
> > Since commit 1751e8a6cb93 ("Rename superblock flags (MS_xyz -> SB_xyz)"),
> > scripts/gdb should be updated to replace MS_xyz with SB_xyz.
> >
> > This change didn't directly affect the running operation of scripts/gdb until
> > commit e262e32d6bde "vfs: Suppress MS_* flag defs within the kernel unless
> 
> Note to stable, e262e32d6bde landed in v5.0-rc1 (which was just
> released), so we'll want this picked back to 5.0 stable once this
> patch hits mainline (akpm just picked it up).
> 
> Just following up to say that without this, debugging a kernel a
> kernel via GDB+QEMU is broken in the 5.0 release.

I do not understand, sorry.  Specifically, what git commits do you want
applied to which stable releases for what reason?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ