public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: carbonated beverage <ramune@net-ronin.org>
To: linux-kernel@vger.kernel.org
Subject: capable open_port() check wrong for kmem
Date: Mon, 9 Dec 2002 19:22:43 -0800	[thread overview]
Message-ID: <20021210032242.GA17583@net-ronin.org> (raw)

hi all,

	I found that I can't open /dev/kmem O_RDONLY.  The open_mem
and open_kmem calls (open_port()) in drivers/char/mem.c checks for
CAP_SYS_RAWIO.

	Is there a possibility of splitting that off into a read and
write pair, i.e. CAP_SYS_RAWIO_WRITE, CAP_SYS_RAWIO_READ?

	If not, is there a way to grant read-only access to /dev/kmem?

-- DN
Daniel

             reply	other threads:[~2002-12-10  3:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  3:22 carbonated beverage [this message]
2002-12-10  5:45 ` capable open_port() check wrong for kmem David Wagner
2002-12-10  6:27   ` David Schwartz
     [not found]   ` <20021210064134.GA17928@net-ronin.org>
2002-12-10  6:51     ` carbonated beverage
2002-12-12  0:43       ` Chris Wright
2002-12-12  1:38         ` carbonated beverage
2002-12-12  2:11           ` Chris Wright
2002-12-10 11:33 ` Olaf Dietsche
2002-12-11 22:38   ` carbonated beverage

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=20021210032242.GA17583@net-ronin.org \
    --to=ramune@net-ronin.org \
    --cc=linux-kernel@vger.kernel.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