From: Greg KH <gregkh@linuxfoundation.org>
To: Lorenz Bauer <lmb@cloudflare.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, kernel-team <kernel-team@cloudflare.com>,
kernel test robot <rong.a.chen@intel.com>
Subject: Re: [PATCH 4.19.y] selftests: bpf: fix use of undeclared RET_IF macro
Date: Wed, 10 Jun 2020 13:49:56 +0200 [thread overview]
Message-ID: <20200610114956.GA1896587@kroah.com> (raw)
In-Reply-To: <CACAyw9-FH7e5fXAU923xSN9ENtyBo+FkqHnd7WAbpyhnz=X9MA@mail.gmail.com>
On Wed, Jun 10, 2020 at 11:16:16AM +0100, Lorenz Bauer wrote:
> On Fri, 22 May 2020 at 01:09, Sasha Levin <sashal@kernel.org> wrote:
> >
> > On Thu, May 21, 2020 at 03:48:41PM +0100, Lorenz Bauer wrote:
> > >commit 634efb750435 ("selftests: bpf: Reset global state between
> > >reuseport test runs") uses a macro RET_IF which doesn't exist in
> > >the v4.19 tree. It is defined as follows:
> > >
> > > #define RET_IF(condition, tag, format...) ({
> > > if (CHECK_FAIL(condition)) {
> > > printf(tag " " format);
> > > return;
> > > }
> > > })
> > >
> > >CHECK_FAIL in turn is defined as:
> > >
> > > #define CHECK_FAIL(condition) ({
> > > int __ret = !!(condition);
> > > int __save_errno = errno;
> > > if (__ret) {
> > > test__fail();
> > > fprintf(stdout, "%s:FAIL:%d\n", __func__, __LINE__);
> > > }
> > > errno = __save_errno;
> > > __ret;
> > > })
> > >
> > >Replace occurences of RET_IF with CHECK. This will abort the test binary
> > >if clearing the intermediate state fails.
> > >
> > >Fixes: 634efb750435 ("selftests: bpf: Reset global state between reuseport test runs")
> > >Reported-by: kernel test robot <rong.a.chen@intel.com>
> > >Signed-off-by: Lorenz Bauer <lmb@cloudflare.com>
> >
> > Thanks for the backport Lorenz. We'll need to wait for it to make it
> > into Linus's tree before queueing up for the stable trees.
>
> Apologies for sending the patch too early (?), I'm still new to this process.
> I've just hit this on 4.19.127. Do you want me to re-submit the patch somewhere?
Is this patch in Linus's tree yet? If so, just tell us the git commit
id. If not, it needs to go there first before we can take it to any
stable tree.
thanks,
greg k-h
next prev parent reply other threads:[~2020-06-10 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 14:48 [PATCH 4.19.y] selftests: bpf: fix use of undeclared RET_IF macro Lorenz Bauer
2020-05-22 0:09 ` Sasha Levin
2020-06-10 10:16 ` Lorenz Bauer
2020-06-10 11:49 ` Greg KH [this message]
2020-06-10 12:10 ` Lorenz Bauer
2020-06-10 12:24 ` Greg KH
2020-06-10 13:34 ` Lorenz Bauer
2020-06-10 13:39 ` Greg KH
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=20200610114956.GA1896587@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernel-team@cloudflare.com \
--cc=lmb@cloudflare.com \
--cc=rong.a.chen@intel.com \
--cc=sashal@kernel.org \
--cc=stable@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