All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+83e7f982ca045ab4405c@syzkaller.appspotmail.com>
To: andrii@kernel.org, bpf@vger.kernel.org, hdanton@sina.com,
	 linux-kernel@vger.kernel.org, mingo@kernel.org,
	 penguin-kernel@i-love.sakura.ne.jp,
	syzkaller-bugs@googlegroups.com,  torvalds@linux-foundation.org
Subject: Re: [syzbot] [bpf?] [trace?] possible deadlock in force_sig_info_to_task
Date: Mon, 29 Apr 2024 04:35:03 -0700	[thread overview]
Message-ID: <000000000000f5a11906173aa4b2@google.com> (raw)
In-Reply-To: <20240429103928.4166-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+83e7f982ca045ab4405c@syzkaller.appspotmail.com

Tested on:

commit:         5eb4573e Merge tag 'soc-fixes-6.9-2' of git://git.kern..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14b4957f180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3d46aa9d7a44f40d
dashboard link: https://syzkaller.appspot.com/bug?extid=83e7f982ca045ab4405c
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=13471b80980000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2024-04-29 11:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  9:05 [syzbot] [bpf?] [trace?] possible deadlock in force_sig_info_to_task syzbot
2024-04-25 17:54 ` Jiri Olsa
2024-04-27 20:00 ` syzbot
2024-04-27 23:13   ` Hillf Danton
2024-04-28 20:01     ` Linus Torvalds
2024-04-28 20:22       ` Linus Torvalds
2024-04-28 23:23       ` Hillf Danton
2024-04-29  0:50         ` Linus Torvalds
2024-04-29  1:00           ` Tetsuo Handa
2024-04-29  1:33           ` Linus Torvalds
2024-04-29  8:00             ` [PATCH] x86/mm: Remove broken vsyscall emulation code from the page fault code Ingo Molnar
2024-04-29 13:51               ` Jiri Olsa
2024-04-29 23:30                 ` Andy Lutomirski
2024-04-29 15:51               ` Linus Torvalds
2024-04-29 18:47                 ` Linus Torvalds
2024-04-29 19:07                   ` Linus Torvalds
2024-04-29 23:29                     ` Andy Lutomirski
2024-04-30  0:05                       ` Linus Torvalds
2024-04-30  6:10                     ` Ingo Molnar
2024-05-01  7:43                       ` Ingo Molnar
2024-04-30 14:53               ` kernel test robot
2024-04-29 10:39             ` [syzbot] [bpf?] [trace?] possible deadlock in force_sig_info_to_task Hillf Danton
2024-04-29 11:35               ` syzbot [this message]
2024-04-30  6:16             ` [tip: x86/urgent] x86/mm: Remove broken vsyscall emulation code from the page fault code tip-bot2 for Linus Torvalds
2024-05-01  7:50             ` tip-bot2 for Linus Torvalds
2024-04-29 14:17           ` [syzbot] [bpf?] [trace?] possible deadlock in force_sig_info_to_task Tetsuo Handa

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=000000000000f5a11906173aa4b2@google.com \
    --to=syzbot+83e7f982ca045ab4405c@syzkaller.appspotmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.