All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Trivial Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [TRIVIAL] Warn users about machines with non-working WP bit
Date: Tue, 06 Aug 2002 13:49:40 +1000	[thread overview]
Message-ID: <20020806035808.710134B71@lists.samba.org> (raw)

[ Truth in advertising? ]

From:  Pavel Machek <pavel@ucw.cz>

  Hi!
  
  This might be good idea, as those machines are not safe for multiuser
  systems.
  

--- trivial-2.5.30/arch/i386/mm/init.c.orig	2002-08-06 13:18:12.000000000 +1000
+++ trivial-2.5.30/arch/i386/mm/init.c	2002-08-06 13:18:12.000000000 +1000
@@ -397,7 +397,7 @@
 	local_flush_tlb();
 
 	if (!boot_cpu_data.wp_works_ok) {
-		printk("No.\n");
+		printk("No (that's security hole).\n");
 #ifdef CONFIG_X86_WP_WORKS_OK
 		panic("This kernel doesn't support CPU's with broken WP. Recompile it for a 386!");
 #endif
-- 
  Don't blame me: the Monkey is driving

             reply	other threads:[~2002-08-06  3:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06  3:49 Rusty Trivial Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-06  9:17 [TRIVIAL] Warn users about machines with non-working WP bit Manfred Spraul
2002-08-06  9:28 ` David S. Miller
2002-08-06  9:42   ` Manfred Spraul
2001-08-20 20:03     ` Pavel Machek
2002-08-06 14:03   ` Kasper Dupont
2002-08-06 13:56     ` David S. Miller
2002-08-06 14:16       ` Kasper Dupont
2002-08-06 14:05         ` David S. Miller
2002-08-06 14:27           ` Kasper Dupont
2002-08-06 14:36             ` Manfred Spraul
2001-08-20 20:06               ` Pavel Machek
2002-08-19 22:04                 ` Alan Cox
2002-08-06 15:11               ` Kasper Dupont
2002-08-06 16:38               ` Willy Tarreau
2002-08-06 16:45               ` Zwane Mwaikambo

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=20020806035808.710134B71@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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 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.