mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+799a2d4576c454ac2693@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] possible deadlock in binder_alloc_free_page
Date: Sun, 12 Jan 2025 09:48:55 +0800	[thread overview]
Message-ID: <20250112014856.1791-1-hdanton@sina.com> (raw)
In-Reply-To: <6782483e.050a0220.216c54.001d.GAE@google.com>

On Sat, 11 Jan 2025 02:30:22 -0800
> syzbot found the following issue on:
> 
> HEAD commit:    7b4b9bf203da Add linux-next specific files for 20250107
> git tree:       linux-next
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10302dc4580000

#syz test

--- x/drivers/android/binder_alloc.c
+++ y/drivers/android/binder_alloc.c
@@ -1245,10 +1245,12 @@ void binder_alloc_init(struct binder_all
 	INIT_LIST_HEAD(&alloc->buffers);
 }
 
+static struct lock_class_key key;
 int binder_alloc_shrinker_init(void)
 {
 	int ret;
 
+	binder_freelist.key = &key;
 	ret = list_lru_init(&binder_freelist);
 	if (ret)
 		return ret;
--- x/fs/debugfs/file.c
+++ y/fs/debugfs/file.c
@@ -87,9 +87,6 @@ static int __debugfs_file_get(struct den
 	if (!((unsigned long)d_fsd & DEBUGFS_FSDATA_IS_REAL_FOPS_BIT)) {
 		fsd = d_fsd;
 	} else {
-		if (WARN_ON(mode == DBGFS_GET_ALREADY))
-			return -EINVAL;
-
 		fsd = kmalloc(sizeof(*fsd), GFP_KERNEL);
 		if (!fsd)
 			return -ENOMEM;
--

  parent reply	other threads:[~2025-01-12  1:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11 10:30 syzbot
2025-01-11 13:15 ` Hillf Danton
2025-01-11 13:32   ` syzbot
2025-01-12  0:11 ` Hillf Danton
2025-01-12  0:33   ` syzbot
2025-01-12  1:48 ` Hillf Danton [this message]
2025-01-12  2:06   ` syzbot
2025-02-19 18:35 ` Carlos Llamas
2025-02-19 18:41   ` Suren Baghdasaryan
2025-03-25  0:41 ` Carlos Llamas

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=20250112014856.1791-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+799a2d4576c454ac2693@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®