From: Richard Weinberger <richard@nod.at>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, ast@kernel.org
Subject: Re: [PATCH 2/3] bpf: Remove dead variable
Date: Mon, 16 Oct 2017 21:22:42 +0200 [thread overview]
Message-ID: <2869131.K5Z6hvSGBl@blindfold> (raw)
In-Reply-To: <59E50473.7040609@iogearbox.net>
Am Montag, 16. Oktober 2017, 21:11:47 CEST schrieb Daniel Borkmann:
> > I can squash it into 1/3, I kept it that way because
> > even without 1/3 this variable is unused.
>
> Hmm, the helper looks like the below. In patch 1/3 you removed
> the 'if (unlikely(!task))' test where the variable was used before,
> so 2/3 without the 1/3 would result in a compile error.
Why a compile error? It emits a warning.
> BPF_CALL_0(bpf_get_current_uid_gid)
> {
> struct task_struct *task = current;
> kuid_t uid;
> kgid_t gid;
>
> if (unlikely(!task))
> return -EINVAL;
Well, this is the only "user". Okay.
> current_uid_gid(&uid, &gid);
Here we use current. So, task was always in vain.
So, I can happily squash 2/3 into 1/3 and resent.
The series just represented the way I've worked on the code...
Thanks,
//richard
next prev parent reply other threads:[~2017-10-16 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 18:18 [PATCH 1/3] bpf: Don't check for current being NULL Richard Weinberger
2017-10-16 18:18 ` [PATCH 2/3] bpf: Remove dead variable Richard Weinberger
2017-10-16 18:54 ` Daniel Borkmann
2017-10-16 18:59 ` Richard Weinberger
2017-10-16 19:11 ` Daniel Borkmann
2017-10-16 19:22 ` Richard Weinberger [this message]
2017-10-16 20:48 ` Daniel Borkmann
2017-10-16 18:18 ` [PATCH 3/3] bpf: Make sure that ->comm does not change under us Richard Weinberger
2017-10-16 20:50 ` Daniel Borkmann
2017-10-16 20:55 ` Richard Weinberger
2017-10-16 21:02 ` Daniel Borkmann
2017-10-16 21:10 ` Richard Weinberger
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=2869131.K5Z6hvSGBl@blindfold \
--to=richard@nod.at \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).