From: Bandan Das <bsd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 4/5] usb-mtp: Introduce write support for MTP objects
Date: Wed, 21 Feb 2018 11:41:31 -0500 [thread overview]
Message-ID: <jpgpo4yjnwk.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <20180221093524.GH17096@redhat.com> ("Daniel P. \=\?utf-8\?Q\?Ber\?\= \=\?utf-8\?Q\?rang\=C3\=A9\=22's\?\= message of "Wed, 21 Feb 2018 09:35:24 +0000")
Daniel P. Berrangé <berrange@redhat.com> writes:
>> #define TYPE_USB_MTP "usb-mtp"
>> @@ -804,6 +815,7 @@ static MTPData *usb_mtp_get_device_info(MTPState *s, MTPControl *c)
>> CMD_GET_OBJECT_HANDLES,
>> CMD_GET_OBJECT_INFO,
>> CMD_DELETE_OBJECT,
>> + CMD_SEND_OBJECT,
>
> Seems we should not advertize this for readonly devices.
Advertising CMD_SEND_OBJECT shows that it's supported but the device is
read-only probably due to a server side setting. It differentiates between
Operation_Not_Supported and Store_Read_Only.
I agree, we should not rely on the initiator to check for this.
I will add a check for readonly when accepting DELETE, OBJECT_INFO
and return the READ_ONLY response code.
Bandan
>> CMD_GET_OBJECT,
>> CMD_GET_PARTIAL_OBJECT,
>> CMD_GET_OBJECT_PROPS_SUPPORTED,
>> @@ -1378,6 +1390,14 @@ static void usb_mtp_command(MTPState *s, MTPControl *c)
>> nres = 1;
>> res0 = data_in->length;
>> break;
>> + case CMD_SEND_OBJECT:
>> + if (!s->write_pending) {
>> + usb_mtp_queue_result(s, RES_INVALID_OBJECTINFO,
>> + c->trans, 0, 0, 0, 0);
>> + return;
>> + }
>> + s->data_out = usb_mtp_data_alloc(c);
>> + return;
>> case CMD_GET_OBJECT_PROPS_SUPPORTED:
>> if (c->argv[0] != FMT_UNDEFINED_OBJECT &&
>> c->argv[0] != FMT_ASSOCIATION) {
>> @@ -1472,12 +1492,126 @@ static void usb_mtp_cancel_packet(USBDevice *dev, USBPacket *p)
>> fprintf(stderr, "%s\n", __func__);
>> }
>>
>> +static void usb_mtp_write_data(MTPState *s)
>> +{
>> + MTPData *d = s->data_out;
>> + MTPObject *parent =
>> + usb_mtp_object_lookup(s, s->dataset.parent_handle);
>> + char *path = NULL;
>> + int rc = -1;
>> + mode_t mask = 0644;
>> +
>> + assert(d != NULL);
>> +
>
>
> Somewhere in here should surely be validating the "readonly" flag.
>
>> + if (parent == NULL || !s->write_pending) {
>> + usb_mtp_queue_result(s, RES_INVALID_OBJECTINFO, d->trans,
>> + 0, 0, 0, 0);
>> + return;
>> + }
>> +
>
> Regards,
> Daniel
next prev parent reply other threads:[~2018-02-21 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 22:58 [Qemu-devel] [PATCH v4 0/5] Initial write support for MTP objects Bandan Das
2018-02-20 22:59 ` [Qemu-devel] [PATCH v4 1/5] usb-mtp: Add one more argument when building results Bandan Das
2018-02-20 22:59 ` [Qemu-devel] [PATCH v4 2/5] usb-mtp: print parent path in IN_IGNORED trace fn Bandan Das
2018-02-20 22:59 ` [Qemu-devel] [PATCH v4 3/5] usb-mtp: Support delete of mtp objects Bandan Das
2018-02-21 9:37 ` Daniel P. Berrangé
2018-02-20 22:59 ` [Qemu-devel] [PATCH v4 4/5] usb-mtp: Introduce write support for MTP objects Bandan Das
2018-02-21 9:35 ` Daniel P. Berrangé
2018-02-21 11:11 ` Gerd Hoffmann
2018-02-21 14:33 ` Daniel P. Berrangé
2018-02-21 16:41 ` Bandan Das [this message]
2018-02-20 22:59 ` [Qemu-devel] [PATCH v4 5/5] usb-mtp: Advertise SendObjectInfo for write support Bandan Das
2018-02-21 9:36 ` Daniel P. Berrangé
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=jpgpo4yjnwk.fsf@linux.bootlegged.copy \
--to=bsd@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).