From: Dan Robertson <danlrobertson89@gmail.com>
To: kieran.bingham@ideasonboard.com, jan.kiszka@siemens.com,
linux-kernel@vger.kernel.org
Cc: Dan Robertson <dan@dlrobertson.com>
Subject: [PATCH 1/1] scripts/gdb: fix linux constants
Date: Mon, 18 Feb 2019 13:25:12 +0000 [thread overview]
Message-ID: <20190218132512.19988-2-dan@dlrobertson.com> (raw)
In-Reply-To: <20190218132512.19988-1-dan@dlrobertson.com>
The linux constants MS_RDONLY, MS_SYNCHRONOUS, MS_MANDLOCK, MS_DIRSYNC,
MS_NOATIME, and MS_NODIRATIME were previously defined in linux/fs.h.
Following e262e32d6bde0f77fb0c95d977482fc872c51996 the constants are
now defined in uapi/linux/mount.h. The new location of the defined
constants needs to be included in constants.py template in order for the
correct constants to be generated.
Fixes: e262e32d6bde ("vfs: Suppress MS_* flag defs within the kernel unless explicitly enabled")
Signed-off-by: Dan Robertson <dan@dlrobertson.com>
---
scripts/gdb/linux/constants.py.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/gdb/linux/constants.py.in b/scripts/gdb/linux/constants.py.in
index 7aad82406422..6c164761d986 100644
--- a/scripts/gdb/linux/constants.py.in
+++ b/scripts/gdb/linux/constants.py.in
@@ -12,9 +12,9 @@
*
*/
-#include <linux/fs.h>
#include <linux/mount.h>
#include <linux/of_fdt.h>
+#include <uapi/linux/mount.h>
/* We need to stringify expanded macros so that they can be parsed */
@@ -36,7 +36,7 @@
import gdb
-/* linux/fs.h */
+/* uapi/linux/mount.h */
LX_VALUE(MS_RDONLY)
LX_VALUE(MS_SYNCHRONOUS)
LX_VALUE(MS_MANDLOCK)
--
2.20.1
prev parent reply other threads:[~2019-02-18 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190215191713.GA28287@nessie>
2019-02-15 20:24 ` [PATCH] scripts/gdb: fix linux constants Kieran Bingham
2019-02-15 20:30 ` Dan Robertson
2019-02-18 13:25 ` [PATCH 0/1] " Dan Robertson
2019-02-18 13:25 ` Dan Robertson [this message]
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=20190218132512.19988-2-dan@dlrobertson.com \
--to=danlrobertson89@gmail.com \
--cc=dan@dlrobertson.com \
--cc=jan.kiszka@siemens.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@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