[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <677bb09e.050a0220.a40f5.000a.GAE@google.com>
Date: Mon, 06 Jan 2025 02:29:50 -0800
From: syzbot <syzbot+ed7c6209f62eba1565aa@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [input?] possible deadlock in input_ff_flush
For archival purposes, forwarding an incoming command email to
linux-kernel@...r.kernel.org.
***
Subject: Re: [syzbot] [input?] possible deadlock in input_ff_flush
Author: hdanton@...a.com
On Sun, 05 Jan 2025 04:40:19 -0800
> syzbot found the following issue on:
>
> HEAD commit: ccb98ccef0e5 Merge tag 'platform-drivers-x86-v6.13-4' of g..
> git tree: upstream
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17bd56df980000
#syz test
--- x/drivers/input/input.c
+++ y/drivers/input/input.c
@@ -642,17 +642,11 @@ EXPORT_SYMBOL(input_open_device);
int input_flush_device(struct input_handle *handle, struct file *file)
{
struct input_dev *dev = handle->dev;
- int retval;
-
- retval = mutex_lock_interruptible(&dev->mutex);
- if (retval)
- return retval;
if (dev->flush)
- retval = dev->flush(dev, file);
+ return dev->flush(dev, file);
- mutex_unlock(&dev->mutex);
- return retval;
+ return 0;
}
EXPORT_SYMBOL(input_flush_device);
--
Powered by blists - more mailing lists