From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guido Kiener <guido@kiener-muenchen.de>
Cc: linux-usb@vger.kernel.org, guido.kiener@rohde-schwarz.com,
pankaj.adhikari@ni.com, steve_bayless@keysight.com,
dpenkler@gmail.com
Subject: [06/12] usb: usbtmc: Add vendor specific/asynchronous read/write ioctls
Date: Fri, 18 May 2018 14:46:15 +0200 [thread overview]
Message-ID: <20180518124615.GC8828@kroah.com> (raw)
On Thu, May 17, 2018 at 07:03:30PM +0200, Guido Kiener wrote:
> +/*
> + * usbtmc_message->flags:
> + */
> +#define USBTMC_FLAG_ASYNC 0x0001
> +#define USBTMC_FLAG_APPEND 0x0002
> +#define USBTMC_FLAG_IGNORE_TRAILER 0x0004
> +
> +struct usbtmc_message {
> + void __user *message; /* pointer to header and data */
> + __u64 transfer_size; /* size of bytes to transfer */
> + __u64 transferred; /* size of received/written bytes */
> + __u32 flags; /* bit 0: 0 = synchronous; 1 = asynchronous */
> +} __attribute__ ((packed));
Very odd structure. Your userspace pointer is going to be totally out
of alignment on 32bit systems running on a 64bit kernel. Why have a
separate pointer at all? Why not just put the mesage at the end of this
structure directly with something like:
__u8 message[0];
?
Much easier and you don't have to mess with the whole compatible ioctl
thunking layer (which I think you ignored here, which means you all
didn't test it...)
thanks,
greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-05-18 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 12:46 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-22 13:37 [06/12] usb: usbtmc: Add vendor specific/asynchronous read/write ioctls Greg Kroah-Hartman
2018-05-22 11:36 Guido Kiener
2018-05-22 10:00 Greg Kroah-Hartman
2018-05-21 20:41 Guido Kiener
2018-05-18 15:13 Guido Kiener
2018-05-18 14:54 Greg Kroah-Hartman
2018-05-18 14:48 Guido Kiener
2018-05-18 14:21 Guido Kiener
2018-05-18 12:44 Greg Kroah-Hartman
2018-05-17 17:03 Guido Kiener
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=20180518124615.GC8828@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dpenkler@gmail.com \
--cc=guido.kiener@rohde-schwarz.com \
--cc=guido@kiener-muenchen.de \
--cc=linux-usb@vger.kernel.org \
--cc=pankaj.adhikari@ni.com \
--cc=steve_bayless@keysight.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.