----- "Stefan Richter" <stefanr@s5r6.in-berlin.de> wrote:
quoted text > Miloslav Trmač wrote:
> > --- /dev/null
> > +++ b/include/linux/ncr.h
> [...]
> > +struct ncr_session_input_data {
> > + const void __user *data;
> > + __kernel_size_t data_size;
> > +};
>
> Why not using fixed-size fit-all members?
>
> struct ncr_session_input_data {
> __u64 data; /* user pointer, cast to/from u64 */
> __u32 data_size; /* or __u64? */
> };
>
> And then get rid of all the COMAPT code paths.
That would make the interface less natural, and any architecture that wanted to have larger pointers (I understand IBM did this back the '80s, so it can happen again) would result in a significantly worse mess than the widely used compat_ioctl mechanism.
Mirek
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: [PATCH 01/19] User-space API definition , Miloslav Trmac , (Sat Aug 21, 2:11 am)