From: "Paul E. McKenney" <paulmck@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/nolibc: always rebuild the sysroot when running a test
Date: Fri, 28 Oct 2022 15:22:14 -0700 [thread overview]
Message-ID: <20221028222214.GU5600@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20221028193405.GA8395@1wt.eu>
On Fri, Oct 28, 2022 at 09:34:05PM +0200, Willy Tarreau wrote:
> Hi Paul,
>
> On Thu, Oct 27, 2022 at 11:26:29AM -0700, Paul E. McKenney wrote:
> > > We'll see, but in any case it would just be a minor detail, but I'll
> > > give you a quick response so that you don't have to deal with multiple
> > > versions of the patch, we all know that it's painful.
> >
> > If I don't hear otherwise from you by the end of tomorrow (Friday),
> > Pacific Time, I will rebase those two patches in preparation for sending
> > a pull request for the regression. I will of course run the pull-message
> > text past you before sending the pull request.
>
> No news on this front, so feel free to pick what you already have.
Very good, thank you!
I currently expect to send something like the pull request shown
below early next week.
Thoughts?
Thanx, Paul
------------------------------------------------------------------------
Hello, Linus,
This pull request fixes a couple of nolibc string-function bugs noted
by kernel test robot, Rasmus Villemoes, Willy Tarreau.
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/nolibc-urgent.2022.10.28a
for you to fetch changes up to b3f4f51ea68a495f8a5956064c33dce711a2df91:
tools/nolibc/string: Fix memcmp() implementation (2022-10-28 15:07:02 -0700)
----------------------------------------------------------------
Urgent nolibc pull request for v6.1
This pull request contains a couple of commits that fix string-function
bugs introduced by:
96980b833a21 ("tools/nolibc/string: do not use __builtin_strlen() at -O0")
66b6f755ad45 ("rcutorture: Import a copy of nolibc")
These appeared in v5.19 and v5.0, respectively, but it would be good
to get these fixes in sooner rather than later. Commits providing the
corresponding tests are in -rcu and I expect to submit them into the
upcoming v6.2 merge window.
----------------------------------------------------------------
Rasmus Villemoes (1):
tools/nolibc/string: Fix memcmp() implementation
Willy Tarreau (1):
tools/nolibc: Fix missing strlen() definition and infinite loop with gcc-12
tools/include/nolibc/string.h | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
next prev parent reply other threads:[~2022-10-28 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 5:45 Willy Tarreau
2022-10-26 16:48 ` Paul E. McKenney
2022-10-26 19:59 ` Willy Tarreau
2022-10-26 20:41 ` Paul E. McKenney
2022-10-27 2:34 ` Willy Tarreau
2022-10-27 17:04 ` Paul E. McKenney
2022-10-27 17:13 ` Willy Tarreau
2022-10-27 18:26 ` Paul E. McKenney
2022-10-28 19:34 ` Willy Tarreau
2022-10-28 22:22 ` Paul E. McKenney [this message]
2022-10-29 5:11 ` Willy Tarreau
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=20221028222214.GU5600@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®