I haven't forgotten about this. I'm doing merges on Wednesday, and will consider this for 5.4/5.5/5.6
Cheers, Bruce On Wed, Mar 4, 2020 at 1:49 AM <[email protected]> wrote: > > From: He Zhe <[email protected]> > > 32-bit user-space program would get errors like the following from ioctl > syscall due to missing compat_ioctl. > MCE_GET_RECORD_LEN: Inappropriate ioctl for device > > compat_ptr_ioctl is provided as a generic implementation of .compat_ioctl > file operation to ioctl functions that either ignore the argument or pass > a pointer to a compatible data type. > > https://lore.kernel.org/lkml/[email protected]/ > > Signed-off-by: He Zhe <[email protected]> > --- > arch/x86/kernel/cpu/mce/dev-mcelog.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/x86/kernel/cpu/mce/dev-mcelog.c > b/arch/x86/kernel/cpu/mce/dev-mcelog.c > index 7c8958d..6c9b91b7 100644 > --- a/arch/x86/kernel/cpu/mce/dev-mcelog.c > +++ b/arch/x86/kernel/cpu/mce/dev-mcelog.c > @@ -328,6 +328,7 @@ static const struct file_operations mce_chrdev_ops = { > .write = mce_chrdev_write, > .poll = mce_chrdev_poll, > .unlocked_ioctl = mce_chrdev_ioctl, > + .compat_ioctl = compat_ptr_ioctl, > .llseek = no_llseek, > }; > > -- > 2.7.4 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8462): https://lists.yoctoproject.org/g/linux-yocto/message/8462 Mute This Topic: https://lists.yoctoproject.org/mt/71720850/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
