mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: linux@weissschuh.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] tools/nolibc: add support for stack protector
Date: Sun, 26 Mar 2023 20:41:29 -0700	[thread overview]
Message-ID: <d186bd6a-e8ed-4a89-875b-6a4406dd1fbc@paulmck-laptop> (raw)
In-Reply-To: <8927157b-bf2c-46b7-a385-f4e230a4777d@paulmck-laptop>

On Sun, Mar 26, 2023 at 11:00:26AM -0700, Paul E. McKenney wrote:
> On Sun, Mar 26, 2023 at 06:55:57PM +0200, Willy Tarreau wrote:
> > On Sun, Mar 26, 2023 at 06:05:15PM +0200, Willy Tarreau wrote:
> > > On Sun, Mar 26, 2023 at 06:00:45PM +0200, Willy Tarreau wrote:
> > > > On Sun, Mar 26, 2023 at 08:45:55AM -0700, Paul E. McKenney wrote:
> > > > > Glad I could "help"!  Timers.  Huh.  ;-)
> > > > > 
> > > > > Checking v6.2, though the rebase is a bit messy, so I won't be all
> > > > > that confident in the results.
> > > > 
> > > > I got the same as you now. I don't know what I missed before not to
> > > > face it, maybe it's the consequence of the rebase. I've re-applied
> > > > the patches on top of 6.2.8 and am retesting now.
> > > > 
> > > > I think you don't need to waste more of your time on this for now
> > > > since we have a reproducer. Thomas and I should take over.
> > > 
> > > And it's a 6.3 regression, as 6.2.8 works fine:
> > > 
> > >   $ make run
> > >   (...)
> > >   Kernel: arch/x86/boot/bzImage is ready  (#2)
> > >   make[1]: Leaving directory '/g/public/linux/master'
> > >   126 test(s) passed.
> > >   $ tail  run.out 
> > >   Errors during this test: 0
> > >   
> > >   Running test 'protection'
> > >   0 -fstackprotector                                               [OK]
> > >   Errors during this test: 0
> > >   
> > >   Total number of errors: 0
> > >   Leaving init with final status: 0
> > >   [    3.388706] ACPI: PM: Preparing to enter system sleep state S5
> > >   [    3.389424] reboot: Power down
> > > 
> > > Now let's have fun bisecting it!
> > 
> > So I have a good news, 6.3-rc1 which dev.2023.03.20a is based on, fails,
> > while 6.3-rc3 works. I haven't got further yet and am not sure it's useful
> > to dig further given that it's an already fixed problem that is not related
> > to the patches in your branch. I don't know if you usually rebase on more
> > recent tags though.
> 
> Thank you for chasing this down!
> 
> In this case, I will at the very least merge with v6.3 before testing.
> I have Joel Fernandes and Boqun Feng trying their hands at running
> the RCU pull request for v6.4, so I will probably resist the urge to
> inject confusion by rebasing onto v6.3-rc1.  ;-)

And merging the -rcu tree's "dev" branch with v6.3-rc3 got me a successful test:

	Kernel: arch/x86/boot/bzImage is ready  (#5)
	make[1]: Leaving directory '/home/git/linux-build'
	125 test(s) passed.

So looking good.  ;-)

								Thanx, Paul

  reply	other threads:[~2023-03-27  3:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25 15:45 Willy Tarreau
2023-03-25 15:45 ` [PATCH 1/8] tools/nolibc: add definitions for standard fds Willy Tarreau
2023-03-25 15:45 ` [PATCH 2/8] tools/nolibc: add helpers for wait() signal exits Willy Tarreau
2023-03-25 15:45 ` [PATCH 3/8] tools/nolibc: tests: constify test_names Willy Tarreau
2023-03-25 15:45 ` [PATCH 4/8] tools/nolibc: add support for stack protector Willy Tarreau
2023-03-25 15:45 ` [PATCH 5/8] tools/nolibc: tests: fold in no-stack-protector cflags Willy Tarreau
2023-03-25 15:45 ` [PATCH 6/8] tools/nolibc: tests: add test for -fstack-protector Willy Tarreau
2023-03-25 15:45 ` [PATCH 7/8] tools/nolibc: i386: add stackprotector support Willy Tarreau
2023-03-25 15:45 ` [PATCH 8/8] tools/nolibc: x86_64: " Willy Tarreau
2023-03-26  4:36 ` [PATCH 0/8] tools/nolibc: add support for stack protector Paul E. McKenney
2023-03-26  6:20   ` Willy Tarreau
2023-03-26 15:13   ` Paul E. McKenney
2023-03-26 15:17     ` Willy Tarreau
2023-03-26 15:26       ` Paul E. McKenney
2023-03-26 15:28         ` Willy Tarreau
2023-03-26 15:45           ` Paul E. McKenney
2023-03-26 16:00             ` Willy Tarreau
2023-03-26 16:05               ` Willy Tarreau
2023-03-26 16:55                 ` Willy Tarreau
2023-03-26 18:00                   ` Paul E. McKenney
2023-03-27  3:41                     ` Paul E. McKenney [this message]
2023-03-27  4:04                       ` Willy Tarreau
2023-03-26 15:30         ` Paul E. McKenney
2023-03-26 15:42           ` 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=d186bd6a-e8ed-4a89-875b-6a4406dd1fbc@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --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®