public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: tim@parrswood.manchester.sch.uk (Tim Fletcher)
Cc: phillips@innominate.de (Daniel Phillips),
	Shawn.Starr@Home.net (Shawn Starr),
	linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at slab.c:1542!(2.4.1-pre9)
Date: Thu, 25 Jan 2001 11:49:10 +0000 (GMT)	[thread overview]
Message-ID: <200101251149.f0PBnB206123@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.30.0101241803290.30141-100000@pine.parrswood.manchester.sch.uk> from "Tim Fletcher" at Jan 24, 2001 06:05:02 PM

Tim Fletcher writes:
> What ever a none privilaged user space apps does witness:
> 
> root@localhost# dd if=/dev/random of=/dev/mem

If you can do that as a non-priviledged user, then you've got bigger
security problems than that.

/dev/mem should NOT be read/writable by anyone other than root.  Its
permissions should be no more than 600.
--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-25 12:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-22 15:23 kernel BUG at slab.c:1542! (2.4.1-pre9) Jorge Nerin
2001-01-22 22:37 ` kernel BUG at slab.c:1542!(2.4.1-pre9) Shawn Starr
2001-01-23  3:02   ` David Ford
2001-01-24 12:58   ` Daniel Phillips
2001-01-24 13:29     ` Gregory Maxwell
2001-01-24 14:32       ` Daniel Phillips
2001-01-24 15:45         ` Andrew Morton
2001-01-25  1:18           ` Alan Cox
2001-01-24 18:05       ` Tim Fletcher
2001-01-24 17:50     ` Shawn Starr
2001-01-24 18:05     ` Tim Fletcher
2001-01-25 11:49       ` Russell King [this message]

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=200101251149.f0PBnB206123@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=Shawn.Starr@Home.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@innominate.de \
    --cc=tim@parrswood.manchester.sch.uk \
    /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