mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+2f44671e54488d20f0e6@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernfs?] [usb?] WARNING in kernfs_get (5)
Date: Wed, 15 May 2024 07:23:19 +0800	[thread overview]
Message-ID: <20240514232319.3252-1-hdanton@sina.com> (raw)
In-Reply-To: <0000000000007224f506186be18b@google.com>

On Tue, 14 May 2024 08:44:43 -0700
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    26dd54d03cd9 Add linux-next specific files for 20240514
> git tree:       linux-next
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14b06900980000

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git  26dd54d03cd9

--- l/drivers/base/firmware_loader/fallback.c
+++ f/drivers/base/firmware_loader/fallback.c
@@ -83,15 +83,15 @@ static int fw_load_sysfs_fallback(struct
 
 	dev_set_uevent_suppress(f_dev, true);
 
+	mutex_lock(&fw_lock);
+
 	retval = device_add(f_dev);
 	if (retval) {
 		dev_err(f_dev, "%s: device_register failed\n", __func__);
 		goto err_put_dev;
 	}
 
-	mutex_lock(&fw_lock);
 	if (fw_load_abort_all || fw_state_is_aborted(fw_priv)) {
-		mutex_unlock(&fw_lock);
 		retval = -EINTR;
 		goto out;
 	}
@@ -120,10 +120,12 @@ static int fw_load_sysfs_fallback(struct
 	} else if (fw_priv->is_paged_buf && !fw_priv->data)
 		retval = -ENOMEM;
 
+	mutex_lock(&fw_lock);
 out:
 	device_del(f_dev);
 err_put_dev:
 	put_device(f_dev);
+	mutex_unlock(&fw_lock);
 	return retval;
 }
 
--

  reply	other threads:[~2024-05-14 23:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 11:07 [syzbot] [kernfs?] " syzbot
2024-05-14 15:44 ` [syzbot] [kernfs?] [usb?] " syzbot
2024-05-14 23:23   ` Hillf Danton [this message]
2024-05-15  1:09     ` syzbot
2024-05-15 10:33   ` Hillf Danton
2024-05-15 18:09     ` syzbot
2024-05-16 14:27   ` Hillf Danton
2024-05-16 14:52     ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240514232319.3252-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+2f44671e54488d20f0e6@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®