On Tue, 30 Aug 2022, Greg Kroah-Hartman wrote:
> On Tue, Aug 30, 2022 at 10:29:56AM +0300, Ilpo Järvinen wrote:
> > -static int serial_rs485_from_user(struct serial_rs485 *rs485,
> > +static int serial_rs485_from_user(struct kserial_rs485 *rs485,
> > const struct serial_rs485 __user *rs485_user)
> > {
> > - if (copy_from_user(rs485, rs485_user, sizeof(*rs485)))
> > + struct serial_rs485 rs485_uapi;
> > +
> > + if (copy_from_user(&rs485_uapi, rs485_user, sizeof(*rs485)))
> > return -EFAULT;
> >
> > + *rs485 = *((struct kserial_rs485 *)&rs485_uapi);
>
> Ah, you are mapping this on top of the existing structure, so there was
> no padding in the original one, why say that?
While I'm not exactly sure what you tried to say with this, I'll try to
answer regardless.
It's the opposite, there's padding in rs485_user, and therefore also in
rs485_uapi. Struct serial_rs485 has padding and is part of uapi so it
cannot be changed to remove the extra padding.
I cannot directly copy_from_user into *rs485 because it lacks the padding.
Thus, the immediate rs485_uapi and then assign to rs485.
> > +/*
> > + * Compile-time asserts for struct kserial_rs485 and struct serial_rs485 equality
> > + * (except padding).
>
> This does not take into account any padding, in fact it's the opposite
> as all of this:
?? I said: "(except padding)" which I thought implies that padding is
intentionally excluded (it doesn't exist in kserial_rs485).
> > + */
> > +static_assert(offsetof(struct kserial_rs485, flags) ==
> > + offsetof(struct serial_rs485, flags));
> > +static_assert(offsetof(struct kserial_rs485, delay_rts_before_send) ==
> > + offsetof(struct serial_rs485, delay_rts_before_send));
> > +static_assert(offsetof(struct kserial_rs485, delay_rts_after_send) ==
> > + offsetof(struct serial_rs485, delay_rts_after_send));
> > +static_assert(offsetof(struct kserial_rs485, addr_recv) ==
> > + offsetof(struct serial_rs485, addr_recv));
> > +static_assert(offsetof(struct kserial_rs485, addr_dest) ==
> > + offsetof(struct serial_rs485, addr_dest));
> > +static_assert(sizeof(struct kserial_rs485) <= sizeof(struct serial_rs485));
>
> Is there to ensure that the offsets are exactly the same, no padding
> involved anywhere.
That's because for kernel padding "doesn't matter", it doesn't want it,
it would be just wasted space. After this series, padding is used only for
uapi, no longer for the in-kernel structs.
> So I don't understand the problem you are trying to solve here,
struct serial_rs485 has padding that is ~16B long currently. serial_rs485
is currently used for a few things:
- Keep track of rs485 state (per port)
- Record what rs485 options the port supports (per port)
- Record rs485 options a driver supports (per driver with rs485 support)
- Exchange rs485 config/state information with userspace
Only the last of those requires the padding (because it has been part of
uapi since day 1). With kserial_rs485, the padding can eliminated for the
first 3 cases.
If you feel ~32B per uart_port too little to be useful (and a little
more per driver), I can just drop this patch.
--
i.
