[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8736f8om96.fsf@toke.dk>
Date: Thu, 31 Oct 2019 18:31:01 +0100
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Andrii Nakryiko <andrii.nakryiko@...il.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
Jesper Dangaard Brouer <brouer@...hat.com>,
David Miller <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH bpf-next v4 2/5] libbpf: Store map pin path and status in struct bpf_map
Andrii Nakryiko <andrii.nakryiko@...il.com> writes:
> [...]
>
>>
>> return err;
>> @@ -4131,17 +4205,24 @@ int bpf_object__unpin_maps(struct bpf_object *obj, const char *path)
>> return -ENOENT;
>>
>> bpf_object__for_each_map(map, obj) {
>> + char *pin_path = NULL;
>> char buf[PATH_MAX];
>
> you can call buf as pin_path and get rid of extra pointer?
The idea here is to end up with bpf_map__unpin(map, NULL) if path is
unset. GCC complains if I reassign a static array pointer, so don't
think I can actually get rid of this?
-Toke
Powered by blists - more mailing lists