From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jeff@garzik.org>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-ide@vger.kernel.org
Subject: Re: [RFC] Read/Write Buffer support
Date: Sat, 15 Mar 2008 23:09:49 +0000 [thread overview]
Message-ID: <20080315230949.785decfb@the-village.bc.nu> (raw)
In-Reply-To: <47DC5223.6080105@garzik.org>
> You arrived at the proper conclusion -- it doesn't happen in practice
> for a variety of reasons, the main one being that it's largely in the
> realm of something the superuser must do intentionally, the way kernel
> and userland code is written today.
Actually thats a serious privilege escalation as it gets you from raw
disk access to cap_sys_rawio so its a security flaw and should be treated
as such even though it is only a minor one in most operating contexts.
Alan
next prev parent reply other threads:[~2008-03-15 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 15:37 [RFC] Read/Write Buffer support Matthew Wilcox
2008-03-15 17:18 ` Jeff Garzik
2008-03-15 17:49 ` Matthew Wilcox
2008-03-15 22:48 ` Jeff Garzik
2008-03-15 23:09 ` Alan Cox [this message]
2008-03-16 0:46 ` Matthew Wilcox
2008-03-16 1:47 ` Jeff Garzik
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=20080315230949.785decfb@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=matthew@wil.cx \
/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;
as well as URLs for NNTP newsgroup(s).