Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1728448 > unrolled thread
| Started by | Seth Forshee <seth.forshee@canonical.com> |
|---|---|
| First post | 2017-09-07 23:30 +0200 |
| Last post | 2017-09-08 01:40 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
seccomp selftest fails to build with glibc 2.26 Seth Forshee <seth.forshee@canonical.com> - 2017-09-07 23:30 +0200
Re: seccomp selftest fails to build with glibc 2.26 Kees Cook <keescook@chromium.org> - 2017-09-08 01:40 +0200
| From | Seth Forshee <seth.forshee@canonical.com> |
|---|---|
| Date | 2017-09-07 23:30 +0200 |
| Subject | seccomp selftest fails to build with glibc 2.26 |
| Message-ID | <uncx4-5G0-5@gated-at.bofh.it> |
Hi Kees, I'm seeing build failures with your seccomp selftest when using glibc 2.26. The first are related to changing macro names from __have_sig*_t to __sig*_t_defined. But after defining those there are more conflicting definitions. I was able to get it to build with the changes below, however it's ugly so I'm hesitant to suggest that it's a fix (and I haven't tested with older glibc either). The full build output is a little lengthy, so I've pasted it at http://pastebin.ubuntu.com/25486192/ rather than including it inline. Thanks, Seth diff --git a/tools/testing/selftests/seccomp/seccomp_bpf.c b/tools/testing/selftests/seccomp/seccomp_bpf.c index 03f1fa49..d234a3e5 100644 --- a/tools/testing/selftests/seccomp/seccomp_bpf.c +++ b/tools/testing/selftests/seccomp/seccomp_bpf.c @@ -11,6 +11,13 @@ #define __have_sigval_t 1 #define __have_sigevent_t 1 +/* These fix errors with glibc 2.26 */ +#define __siginfo_t_defined 1 +#define __sigval_t_defined 1 +#define __sigevent_t_defined 1 +#define _BITS_SIGINFO_CONSTS_H 1 +#define _BITS_SIGEVENT_CONSTS_H 1 + #include <errno.h> #include <linux/filter.h> #include <sys/prctl.h>
[toc] | [next] | [standalone]
| From | Kees Cook <keescook@chromium.org> |
|---|---|
| Date | 2017-09-08 01:40 +0200 |
| Message-ID | <uneyR-6Vy-5@gated-at.bofh.it> |
| In reply to | #1728448 |
On Thu, Sep 7, 2017 at 2:27 PM, Seth Forshee <seth.forshee@canonical.com> wrote: > Hi Kees, > > I'm seeing build failures with your seccomp selftest when using glibc > 2.26. The first are related to changing macro names from __have_sig*_t > to __sig*_t_defined. But after defining those there are more conflicting > definitions. I was able to get it to build with the changes below, > however it's ugly so I'm hesitant to suggest that it's a fix (and I > haven't tested with older glibc either). > > The full build output is a little lengthy, so I've pasted it at > http://pastebin.ubuntu.com/25486192/ rather than including it inline. Thanks for the details! I took a different route for the solution (basically, we can drop the hack for glibc not having support for SIGSYS in its siginfo_t), and sent a separate email with the patch. -Kees > > Thanks, > Seth > > > diff --git a/tools/testing/selftests/seccomp/seccomp_bpf.c b/tools/testing/selftests/seccomp/seccomp_bpf.c > index 03f1fa49..d234a3e5 100644 > --- a/tools/testing/selftests/seccomp/seccomp_bpf.c > +++ b/tools/testing/selftests/seccomp/seccomp_bpf.c > @@ -11,6 +11,13 @@ > #define __have_sigval_t 1 > #define __have_sigevent_t 1 > > +/* These fix errors with glibc 2.26 */ > +#define __siginfo_t_defined 1 > +#define __sigval_t_defined 1 > +#define __sigevent_t_defined 1 > +#define _BITS_SIGINFO_CONSTS_H 1 > +#define _BITS_SIGEVENT_CONSTS_H 1 > + > #include <errno.h> > #include <linux/filter.h> > #include <sys/prctl.h> -- Kees Cook Pixel Security
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web