[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220118202308.2imtkkif4sagb22e@ast-mbp.dhcp.thefacebook.com>
Date: Tue, 18 Jan 2022 12:23:08 -0800
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Lorenzo Bianconi <lorenzo@...nel.org>
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org,
lorenzo.bianconi@...hat.com, davem@...emloft.net, kuba@...nel.org,
ast@...nel.org, daniel@...earbox.net, shayagr@...zon.com,
john.fastabend@...il.com, dsahern@...nel.org, brouer@...hat.com,
echaudro@...hat.com, jasowang@...hat.com,
alexander.duyck@...il.com, saeed@...nel.org,
maciej.fijalkowski@...el.com, magnus.karlsson@...el.com,
tirthendu.sarkar@...el.com, toke@...hat.com
Subject: Re: [PATCH v22 bpf-next 19/23] bpf: generalise tail call map
compatibility check
On Mon, Jan 17, 2022 at 06:28:31PM +0100, Lorenzo Bianconi wrote:
> seq_printf(m,
> @@ -590,6 +589,7 @@ static void bpf_map_show_fdinfo(struct seq_file *m, struct file *filp)
> if (type) {
> seq_printf(m, "owner_prog_type:\t%u\n", type);
> seq_printf(m, "owner_jited:\t%u\n", jited);
> + seq_printf(m, "owner_xdp_has_frags:\t%u\n", xdp_has_frags);
Internal flag shouldn't be printed in fdinfo.
In particular it's not correct for non-xdp progs.
Powered by blists - more mailing lists