mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master] lib: stackprotector: adjust Kconfig text for barebox
Date: Wed,  3 Jan 2024 11:13:24 +0100	[thread overview]
Message-ID: <20240103101324.2628829-1-a.fatoum@pengutronix.de> (raw)

The reference to kernel panic is taken from the original Linux Kconfig
help text. Leaving it as-is may be confusing, so adjust it for barebox.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 lib/Kconfig.hardening | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/Kconfig.hardening b/lib/Kconfig.hardening
index f14b256a7d91..7f74d0d98a9c 100644
--- a/lib/Kconfig.hardening
+++ b/lib/Kconfig.hardening
@@ -30,7 +30,7 @@ config STACKPROTECTOR_STRONG
 	  the value just before actually returning.  Stack based buffer
 	  overflows (that need to overwrite this return address) now also
 	  overwrite the canary, which gets detected and the attack is then
-	  neutralized via a kernel panic.
+	  neutralized via a barebox panic.
 
 	  Functions will have the stack-protector canary logic added in any
 	  of the following conditions:
@@ -78,7 +78,7 @@ config PBL_STACKPROTECTOR_STRONG
 	  the value just before actually returning.  Stack based buffer
 	  overflows (that need to overwrite this return address) now also
 	  overwrite the canary, which gets detected and the attack is then
-	  neutralized via a kernel panic.
+	  neutralized via a barebox panic.
 
 	  Functions will have the stack-protector canary logic added in any
 	  of the following conditions:
-- 
2.39.2




             reply	other threads:[~2024-01-03 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 10:13 Ahmad Fatoum [this message]
2024-01-03 14:09 ` Sascha Hauer

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=20240103101324.2628829-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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