From: guoren@kernel.org
To: palmer@rivosinc.com, arnd@arndb.de, linux@roeck-us.net,
palmer@dabbelt.com, heiko@sntech.de
Cc: linux-riscv@lists.infradead.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>,
Eugene Syromiatnikov <esyr@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: [PATCH] uapi: Fixup strace compile error
Date: Sun, 12 Jun 2022 21:30:51 -0400 [thread overview]
Message-ID: <20220613013051.1741434-1-guoren@kernel.org> (raw)
From: Guo Ren <guoren@linux.alibaba.com>
There is no CONFIG_64BIT in userspace, we shouldn't limit it with
__BITS_PER_LONG == 32 to break the compatibility. Just export F_*64
definitions to userspace permanently.
gcc-11 -DHAVE_CONFIG_H -I./linux/x86_64 -I../../../src/linux/x86_64
-I./linux/generic -I../../../src/linux/generic -I. -I../../../src
-DIN_STRACE=1 -isystem /opt/kernel/include -Wall -Wextra
-Wno-missing-field-initializers -Wno-unused-parameter -Wdate-time
-Wformat-security -Wimplicit-fallthrough=5 -Winit-self -Wlogical-op
-Wmissing-prototypes -Wnested-externs -Wold-style-definition
-Wtrampolines -Wundef -Wwrite-strings -Werror -g -O2 -c -o
libstrace_a-fetch_bpf_fprog.o `test -f 'fetch_bpf_fprog.c' || echo
'../../../src/'`fetch_bpf_fprog.c
In file included from ../../../src/defs.h:404,
from ../../../src/fcntl.c:12:
../../../src/xlat/fcntlcmds.h:54:7: error: ‘F_GETLK64’ undeclared here
(not in a function); did you mean ‘F_GETLK’?
54 | XLAT(F_GETLK64),
| ^~~~~~~~~
../../../src/xlat.h:64:54: note: in definition of macro ‘XLAT’
64 | # define XLAT(val) { (unsigned)(val), #val
}
| ^~~
../../../src/xlat/fcntlcmds.h:57:7: error: ‘F_SETLK64’ undeclared here
(not in a function); did you mean ‘F_SETLK’?
57 | XLAT(F_SETLK64),
| ^~~~~~~~~
../../../src/xlat.h:64:54: note: in definition of macro ‘XLAT’
64 | # define XLAT(val) { (unsigned)(val), #val
}
| ^~~
../../../src/xlat/fcntlcmds.h:60:7: error: ‘F_SETLKW64’ undeclared here
(not in a function); did you mean ‘F_SETLKW’?
60 | XLAT(F_SETLKW64),
| ^~~~~~~~~~
../../../src/xlat.h:64:54: note: in definition of macro ‘XLAT’
64 | # define XLAT(val) { (unsigned)(val), #val
}
| ^~~
make[4]: *** [Makefile:5017: libstrace_a-fcntl.o] Error 1
comment by Eugene:
Actually, it's quite the opposite: "ifndef" usage made it vailable at all
times to the userspace, and this change has actually broken building strace
with the latest kernel headers[1][2]. There could be some debate whether
having these F_*64 definitions exposed to the user space 64-bit
applications, but it seems that were no harm (as they were exposed already
for quite some time), and they are useful at least for strace for compat
application tracing purposes.
Fixes: 306f7cc1e9061 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"
Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
Reported-by: Eugene Syromiatnikov <esyr@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Heiko Stuebner <heiko@sntech.de>
Cc: Palmer Dabbelt <palmer@rivosinc.com>
---
include/uapi/asm-generic/fcntl.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/uapi/asm-generic/fcntl.h b/include/uapi/asm-generic/fcntl.h
index f13d37b60775..cd6bd65ec25d 100644
--- a/include/uapi/asm-generic/fcntl.h
+++ b/include/uapi/asm-generic/fcntl.h
@@ -116,13 +116,11 @@
#define F_GETSIG 11 /* for sockets. */
#endif
-#if __BITS_PER_LONG == 32 || defined(__KERNEL__)
#ifndef F_GETLK64
#define F_GETLK64 12 /* using 'struct flock64' */
#define F_SETLK64 13
#define F_SETLKW64 14
#endif
-#endif /* __BITS_PER_LONG == 32 || defined(__KERNEL__) */
#ifndef F_SETOWN_EX
#define F_SETOWN_EX 15
--
2.36.1
next reply other threads:[~2022-06-13 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 1:30 guoren [this message]
2022-06-13 13:58 ` [PATCH] uapi: Fixup strace compile error Heiko Stübner
2022-08-04 2:10 ` Guo Ren
2022-06-13 14:29 ` Christoph Hellwig
2022-08-04 0:40 ` Palmer Dabbelt
2022-08-04 2:12 ` Guo Ren
2022-08-04 2:09 ` Guo Ren
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=20220613013051.1741434-1-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=arnd@arndb.de \
--cc=esyr@redhat.com \
--cc=guoren@linux.alibaba.com \
--cc=hch@lst.de \
--cc=heiko@sntech.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
/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