[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180601084114.xgvtg7nmihdavnnd@ast-mbp>
Date: Fri, 1 Jun 2018 04:41:16 -0400
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Eugene Syromiatnikov <esyr@...hat.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, Martin KaFai Lau <kafai@...com>,
Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jiri Olsa <jolsa@...nel.org>, Ingo Molnar <mingo@...nel.org>,
Lawrence Brakmo <brakmo@...com>, Andrey Ignatov <rdna@...com>,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
John Fastabend <john.fastabend@...il.com>
Subject: Re: [PATCH bpf 1/2] bpf: fix alignment of netns_dev/netns_ino fields
in bpf_{map,prog}_info
On Fri, Jun 01, 2018 at 06:12:10AM +0300, Dmitry V. Levin wrote:
> Hi,
>
> Looks like the ABI bug in bpf_map_info and bpf_prog info introduced
> in 4.16 is going to slip into 4.17, causing extra pain to 32-bit
> userspace. I'm adding Linus to this thread in hope it might help
> to get a fix applied before 4.17 is released.
The issue identified in patch 1 is valid.
These two fields won't be properly accessible by 32-bit user space
on 64-bit kernel.
But the fix in patch 1 is wrong.
The patch 2 is completely unnecessary.
Everyone can also see that the patches are still marked as 'new' in patchworks
meaning that we didn't process them.
At the moment many networking folks are traveling to netconf
and we only had a chance to discuss this set last night.
We'll try to send a fix in coming days.
But regardless whether 4.17 is realesed this sunday or not
we're not going to rush wrong patch in without proper code review
and discussion.
That future patch either will land in 4.17 (if it's dealyed into next sunday)
or it will be sent to stable.
To speed up the situation next time please report the issue that you find
to public netdev mailing list instead of using proprietary distro emails.
Thanks.
> On Wed, May 30, 2018 at 09:18:58PM +0300, Dmitry V. Levin wrote:
> > On Sun, May 27, 2018 at 01:28:42PM +0200, Eugene Syromiatnikov wrote:
> > > Recent introduction of netns_dev/netns_ino to bpf_map_info/bpf_prog info
> > > has broken compat, as offsets of these fields are different in 32-bit
> > > and 64-bit ABIs. One fix (other than implementing compat support in
> > > syscall in order to handle this discrepancy) is to use __aligned_u64
> > > instead of __u64 for these fields.
> > >
> > > Reported-by: Dmitry V. Levin <ldv@...linux.org>
> > > Fixes: 52775b33bb507 ("bpf: offload: report device information about
> > > offloaded maps")
> > > Fixes: 675fc275a3a2d ("bpf: offload: report device information for
> > > offloaded programs")
> > >
> > > Signed-off-by: Eugene Syromiatnikov <esyr@...hat.com>
> >
> > Reviewed-by: "Dmitry V. Levin" <ldv@...linux.org>
> > Cc: <stable@...r.kernel.org> # v4.16+
> >
> > Thanks,
> >
> > > ---
> > > include/uapi/linux/bpf.h | 8 ++++----
> > > tools/include/uapi/linux/bpf.h | 8 ++++----
> > > 2 files changed, 8 insertions(+), 8 deletions(-)
> > >
> > > diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
> > > index c5ec897..903010a 100644
> > > --- a/include/uapi/linux/bpf.h
> > > +++ b/include/uapi/linux/bpf.h
> > > @@ -1017,8 +1017,8 @@ struct bpf_prog_info {
> > > __aligned_u64 map_ids;
> > > char name[BPF_OBJ_NAME_LEN];
> > > __u32 ifindex;
> > > - __u64 netns_dev;
> > > - __u64 netns_ino;
> > > + __aligned_u64 netns_dev;
> > > + __aligned_u64 netns_ino;
> > > } __attribute__((aligned(8)));
> > >
> > > struct bpf_map_info {
> > > @@ -1030,8 +1030,8 @@ struct bpf_map_info {
> > > __u32 map_flags;
> > > char name[BPF_OBJ_NAME_LEN];
> > > __u32 ifindex;
> > > - __u64 netns_dev;
> > > - __u64 netns_ino;
> > > + __aligned_u64 netns_dev;
> > > + __aligned_u64 netns_ino;
> > > } __attribute__((aligned(8)));
> > >
> > > /* User bpf_sock_addr struct to access socket fields and sockaddr struct passed
> > > diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h
> > > index c5ec897..903010a 100644
> > > --- a/tools/include/uapi/linux/bpf.h
> > > +++ b/tools/include/uapi/linux/bpf.h
> > > @@ -1017,8 +1017,8 @@ struct bpf_prog_info {
> > > __aligned_u64 map_ids;
> > > char name[BPF_OBJ_NAME_LEN];
> > > __u32 ifindex;
> > > - __u64 netns_dev;
> > > - __u64 netns_ino;
> > > + __aligned_u64 netns_dev;
> > > + __aligned_u64 netns_ino;
> > > } __attribute__((aligned(8)));
> > >
> > > struct bpf_map_info {
> > > @@ -1030,8 +1030,8 @@ struct bpf_map_info {
> > > __u32 map_flags;
> > > char name[BPF_OBJ_NAME_LEN];
> > > __u32 ifindex;
> > > - __u64 netns_dev;
> > > - __u64 netns_ino;
> > > + __aligned_u64 netns_dev;
> > > + __aligned_u64 netns_ino;
> > > } __attribute__((aligned(8)));
> > >
> > > /* User bpf_sock_addr struct to access socket fields and sockaddr struct passed
>
>
> --
> ldv
Powered by blists - more mailing lists