[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANp29Y6ge-AhM+Byt3imGOpctRsgWiqBN-reuKvOJAzxBsTYLw@mail.gmail.com>
Date: Thu, 23 Nov 2023 10:32:26 +0100
From: Aleksandr Nogikh <nogikh@...gle.com>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Cc: xingwei lee <xrivendell7@...il.com>,
"syzbot+786b124fe4ce4dc99357@...kaller.appspotmail.com"
<syzbot+786b124fe4ce4dc99357@...kaller.appspotmail.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"rafael@...nel.org" <rafael@...nel.org>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>,
Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [syzbot] [kernel?] general protection fault in joydev_connect
On Thu, Nov 23, 2023 at 9:55 AM gregkh@...uxfoundation.org
<gregkh@...uxfoundation.org> wrote:
>
> On Wed, Nov 22, 2023 at 07:55:50PM +0800, xingwei lee wrote:
> > Hi. I have reproduced this bug with repro.txt and repro.c below:
> >
> > repro.txt
> > r0 = openat$uinput(0xffffffffffffff9c, &(0x7f0000000500), 0x802, 0x0)
> > ioctl$UI_DEV_SETUP(r0, 0x405c5503, &(0x7f0000000080)={{0x0, 0xffff,
> > 0x3}, 'syz0\x00'})
> > ioctl$UI_DEV_CREATE(r0, 0x5501) (fail_nth: 51)
>
> You are using fault injection, which, by it's very name, causes faults :)
But those injected failures (that do not break the kernel, but just
emulate an error returned from a function that should be expected to
sometimes return an error) still should not lead to general protection
fault panics, shouldn't they?
--
Aleksandr
>
> Can you reproduce it without causing faults in the kernel? And if so,
> can you create a patch to fix this?
>
> thanks,
>
> greg k-h
>
Powered by blists - more mailing lists