From: Arnd Bergmann <arnd@arndb.de>
To: "Michał Mirosław" <mirqus@gmail.com>
Cc: John Calixto <john.calixto@modsystems.com>,
linux-mmc@vger.kernel.org, cjb@laptop.org
Subject: Re: [PATCH resend] mmc: Added ioctl to let userspace apps send ACMD
Date: Mon, 21 Mar 2011 13:25:34 +0100 [thread overview]
Message-ID: <201103211325.34785.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTim9PXg8UXMkDXUQ6W9pYp12U6MQ2AR+3ORk-uEX@mail.gmail.com>
On Sunday 20 March 2011, Michał Mirosław wrote:
> 2011/3/20 John Calixto <john.calixto@modsystems.com>:
> > On Sat, 19 Mar 2011, Arnd Bergmann wrote:
> [...]
> >> > I expect for more general purposes, like your qemu passthrough case, you
> >> > would want to add a handler for cmd=SD_IOC_CMD?
> >> Yes, but I suspect that would mean blocking all other activity on the
> >> same device, possibly with an ioctl for claiming the host for an
> >> extended period of time.
> > Sure. And if the testing I described above shows that regular block
> > operations are indeed negatively affected, then I'll have to implement
> > that ioctl for claiming the host myself and you'll have a head start! :)
>
> This idea is scary. ;-) Just think what would happen if userspace made
> this sequence:
> 1. fd = open(dev)
> 2. ioctl(fd, claim host)
> 3. read(fd, ...)
>
> (if 3. is not convincing, replace it with any access to mounted
> filesystem from the same card.)
I agree. If we allow such a command on a block device, that
should probably be mutually exclusive with normal read/write
access or mounting the block device, and it needs to be a
priviledged operation.
Arnd
next prev parent reply other threads:[~2011-03-21 12:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 18:28 [PATCH resend] mmc: Added ioctl to let userspace apps send ACMDs John Calixto
2011-03-17 18:35 ` Ben Dooks
2011-03-17 21:55 ` Arnd Bergmann
2011-03-18 17:32 ` John Calixto
2011-03-18 17:56 ` Michał Mirosław
2011-03-18 19:26 ` Arnd Bergmann
2011-03-19 17:36 ` Michał Mirosław
2011-03-19 19:00 ` Arnd Bergmann
2011-03-21 18:37 ` John Calixto
2011-03-21 23:16 ` Michał Mirosław
2011-03-22 22:31 ` John Calixto
2011-03-23 0:18 ` Michał Mirosław
2011-03-23 0:44 ` John Calixto
2011-03-23 7:57 ` Arnd Bergmann
2011-03-18 19:25 ` Arnd Bergmann
2011-03-18 22:06 ` [PATCH resend] mmc: Added ioctl to let userspace apps send ACMD John Calixto
2011-03-19 11:52 ` Arnd Bergmann
2011-03-20 2:12 ` John Calixto
2011-03-20 5:11 ` Michał Mirosław
2011-03-21 12:25 ` Arnd Bergmann [this message]
2011-03-21 14:26 ` Andrei Warkentin
2011-03-21 18:22 ` John Calixto
2011-03-19 0:24 ` [PATCH resend] mmc: Added ioctl to let userspace apps send ACMDs John Calixto
2011-03-19 9:42 ` Arnd Bergmann
2011-03-19 16:09 ` Chris Ball
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=201103211325.34785.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=john.calixto@modsystems.com \
--cc=linux-mmc@vger.kernel.org \
--cc=mirqus@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox