linux-kernel - [PATCH 0/1] tools/nolibc: tests: use volatile to force stack smashing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230328161845.9584-1-w@1wt.eu>
Date:   Tue, 28 Mar 2023 18:18:44 +0200
From:   Willy Tarreau <w@....eu>
To:     "Paul E. McKenney" <paulmck@...nel.org>
Cc:     linux@...ssschuh.net, linux-kernel@...r.kernel.org,
        Alexey Dobriyan <adobriyan@...il.com>, Willy Tarreau <w@....eu>
Subject: [PATCH 0/1] tools/nolibc: tests: use volatile to force stack smashing

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