All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+f2c4e7bfcca6c6d6324c@syzkaller.appspotmail.com>,
	jstultz@google.com, linux-kernel@vger.kernel.org,
	sboyd@kernel.org, syzkaller-bugs@googlegroups.com,
	peterz@infraded.org
Subject: Re: [syzbot] [kernel?] possible deadlock in alarm_handle_timer
Date: Tue, 12 Dec 2023 20:22:56 +0100	[thread overview]
Message-ID: <87le9zp6nj.ffs@tglx> (raw)
In-Reply-To: <00000000000095a67c060a59bdce@google.com>

On Fri, Nov 17 2023 at 06:13, syzbot wrote:
> HEAD commit:    eff99d8edbed Add linux-next specific files for 20231117
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=134b7d84e80000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=61991b2630c19677
> dashboard link: https://syzkaller.appspot.com/bug?extid=f2c4e7bfcca6c6d6324c
> compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.

Offending commit

  5431fdd2c181 ("ptrace: Convert ptrace_attach() to use lock guards")

got removed from linux-next 2023-11-20.

#syz invalid

  reply	other threads:[~2023-12-12 19:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 14:13 [syzbot] [kernel?] possible deadlock in alarm_handle_timer syzbot
2023-12-12 19:22 ` Thomas Gleixner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-05  2:07 xingwei lee
2023-12-08 21:42 ` Thomas Gleixner
2023-12-09  3:08   ` xingwei lee
2023-12-12 19:19     ` Thomas Gleixner

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=87le9zp6nj.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infraded.org \
    --cc=sboyd@kernel.org \
    --cc=syzbot+f2c4e7bfcca6c6d6324c@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 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.