mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+69c74d38464686431506@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in copy_process
Date: Thu, 28 Aug 2025 15:38:31 +0800	[thread overview]
Message-ID: <20250828073832.5955-1-hdanton@sina.com> (raw)
In-Reply-To: <68af9193.a00a0220.2929dc.0006.GAE@google.com>

> Date: Wed, 27 Aug 2025 16:15:31 -0700	[thread overview]
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    7fa4d8dc380f Add linux-next specific files for 20250821
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1036def0580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=ae76068823a236b3
> dashboard link: https://syzkaller.appspot.com/bug?extid=69c74d38464686431506
> compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13595c62580000

#syz test

--- x/mm/oom_kill.c
+++ y/mm/oom_kill.c
@@ -997,6 +997,8 @@ static void __oom_kill_process(struct ta
 		queue_oom_reaper(victim);
 
 	mmdrop(mm);
+	write_lock_irq(&tasklist_lock);
+	write_unlock_irq(&tasklist_lock);
 	put_task_struct(victim);
 }
 
@@ -1031,6 +1033,8 @@ static void oom_kill_process(struct oom_
 		mark_oom_victim(victim);
 		queue_oom_reaper(victim);
 		task_unlock(victim);
+		write_lock_irq(&tasklist_lock);
+		write_unlock_irq(&tasklist_lock);
 		put_task_struct(victim);
 		return;
 	}
--

  reply	other threads:[~2025-08-28  7:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25  3:00 syzbot
2025-08-25 15:50 ` David Hildenbrand
2025-08-28 13:12   ` Hillf Danton
2025-08-27 23:15 ` syzbot
2025-08-28  7:38   ` Hillf Danton [this message]
2025-08-28  8:50     ` syzbot
2025-08-28 11:47   ` Hillf Danton
2025-08-28 12:18     ` 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=20250828073832.5955-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+69c74d38464686431506@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®