From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Jackie Liu <liuyun01@kylinos.cn>,
Kieran Bingham <kbingham@kernel.org>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Dan Robertson <danlrobertson89@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH v3] scripts/gdb: replace flags (MS_xyz -> SB_xyz)
Date: Fri, 8 Mar 2019 13:36:55 +0100 [thread overview]
Message-ID: <20190308123655.GA13818@kroah.com> (raw)
In-Reply-To: <CAKwvOdnOuXhkwizSnp6qOwJkisHKEBs=2xSvHaus3Yhdx2xE-w@mail.gmail.com>
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@ideasonboard.com> wrote:
> >
> > From: Jackie Liu <liuyun01@kylinos.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
next prev parent reply other threads:[~2019-03-08 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 10:30 [PATCH v3] scripts/gdb: replace flags (MS_xyz -> SB_xyz) Kieran Bingham
2019-03-05 21:47 ` Nick Desaulniers
2019-03-08 12:36 ` Greg KH [this message]
2019-03-08 20:56 ` Nick Desaulniers
2019-03-12 12:50 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190308123655.GA13818@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=danlrobertson89@gmail.com \
--cc=felipe.balbi@linux.intel.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyun01@kylinos.cn \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).