From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Hatayama, Daisuke" <d.hatayama@jp.fujitsu.com>
Cc: "'marcandre.lureau@redhat.com'" <marcandre.lureau@redhat.com>,
"'somlo@cmu.edu'" <somlo@cmu.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"'qemu-devel@nongnu.org'" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v3 5/5] RFC: fw_cfg: add DMA write operation in sysfs
Date: Mon, 30 Oct 2017 18:19:21 +0200 [thread overview]
Message-ID: <20171030181711-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <33710E6CAA200E4583255F4FB666C4E21B120583@G01JPEXMBYT03>
On Mon, Oct 30, 2017 at 11:07:20AM +0000, Hatayama, Daisuke wrote:
> > From: Marc-André Lureau <marcandre.lureau@redhat.com>
> >
> > Since qemu 2.9, DMA write operations are allowed. However, usage of this
> > interface from kernel or user-space is strongly discouraged by the
> > maintainers. This patch is meant for experimentations for now.
> >
>
> Could you (or maintainers?) tell me how experimental the DMA write
> operations from kernel are?
>
> From some technical reason?
> Or simply there has not been enough test yet so far?
The concern is security, talking from userspace to hypervisor
might become a trivial DOS vector.
If there's need for a specific entry to be accessible from userspace,
I'd rather white-list it.
> > Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> > ---
> > drivers/firmware/qemu_fw_cfg.c | 21 ++++++++++++++++++++-
> > 1 file changed, 20 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/firmware/qemu_fw_cfg.c b/drivers/firmware/qemu_fw_cfg.c
> > index 54b569da3257..e2f2ad1c9c0c 100644
> > --- a/drivers/firmware/qemu_fw_cfg.c
> > +++ b/drivers/firmware/qemu_fw_cfg.c
> > @@ -524,9 +524,28 @@ static ssize_t fw_cfg_sysfs_read_raw(struct file *filp, struct kobject *kobj,
> > return fw_cfg_read_blob(entry->f.select, buf, pos, count, true);
> > }
> >
> > +static ssize_t fw_cfg_sysfs_write_raw(struct file *filp, struct kobject *kobj,
> > + struct bin_attribute *bin_attr,
> > + char *buf, loff_t pos, size_t count)
> > +{
> > + struct fw_cfg_sysfs_entry *entry = to_entry(kobj);
> > +
> > + if (!fw_cfg_dma_enabled())
> > + return -ENOTSUPP;
> > +
> > + if (pos > entry->f.size)
> > + return -EINVAL;
> > +
> > + if (count > entry->f.size - pos)
> > + count = entry->f.size - pos;
> > +
> > + return fw_cfg_write_blob(entry->f.select, buf, pos, count);
> > +}
> > +
> > static struct bin_attribute fw_cfg_sysfs_attr_raw = {
> > - .attr = { .name = "raw", .mode = S_IRUSR },
> > + .attr = { .name = "raw", .mode = S_IRUSR | S_IWUSR },
> > .read = fw_cfg_sysfs_read_raw,
> > + .write = fw_cfg_sysfs_write_raw,
> > };
> >
> > /*
> > --
> > 2.14.1.146.gd35faa819
>
> Thanks.
> HATAYAMA, Daisuke
>
next prev parent reply other threads:[~2017-10-30 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 11:07 [PATCH v3 5/5] RFC: fw_cfg: add DMA write operation in sysfs Hatayama, Daisuke
2017-10-30 16:19 ` Michael S. Tsirkin [this message]
2017-10-31 9:55 ` Hatayama, Daisuke
2017-10-31 17:06 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2017-09-22 13:24 [PATCH v3 0/5] fw_cfg: add DMA operations & etc/vmcoreinfo support marcandre.lureau
2017-09-22 13:24 ` [PATCH v3 5/5] RFC: fw_cfg: add DMA write operation in sysfs marcandre.lureau
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=20171030181711-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
/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