All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/1] tools/nolibc: tests: use volatile to force stack smashing
@ 2023-03-28 16:18 Willy Tarreau
  2023-03-28 16:18 ` [PATCH 1/1] " Willy Tarreau
  2023-03-28 18:29 ` [PATCH 0/1] " Paul E. McKenney
  0 siblings, 2 replies; 5+ messages in thread
From: Willy Tarreau @ 2023-03-28 16:18 UTC (permalink / raw)
  To: Paul E. McKenney; +Cc: linux, linux-kernel, Alexey Dobriyan, Willy Tarreau

Hello Paul,

as previously discussed after Alexey's report, Thomas updated his stack
smashing code to use a volatile pointer instead of dropping compiler
optimizations. It's both cleaner and safer this way.

I verified on all supported archs that it doesn't change the behavior
and passes the test without issues, so I'm fine with it:

  125 test(s) passed.

It can be queued on top of the existing series either for the next merge
or the one after at your convenience, as I know that you're running long
and complete tests with your series, and I don't want to make you change
your tests at the last minute. This one is not urgent at all, it's more
of a maintenance improvement anyway.

Thank you!
Willy

Thomas Weißschuh (1):
  tools/nolibc: tests: use volatile to force stack smashing

 tools/testing/selftests/nolibc/nolibc-test.c | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

-- 
2.17.5


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2023-03-28 20:01 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-28 16:18 [PATCH 0/1] tools/nolibc: tests: use volatile to force stack smashing Willy Tarreau
2023-03-28 16:18 ` [PATCH 1/1] " Willy Tarreau
2023-03-28 18:29 ` [PATCH 0/1] " Paul E. McKenney
2023-03-28 18:51   ` Willy Tarreau
2023-03-28 20:01     ` Paul E. McKenney

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.