All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+5fd924f4cd9dc1c7828c@syzkaller.appspotmail.com>,
	frederic@kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] possible deadlock in exit_itimers
Date: Sun, 18 Jun 2023 22:44:36 +0200	[thread overview]
Message-ID: <87v8fkqz4b.ffs@tglx> (raw)
In-Reply-To: <000000000000cf863605fe4c5f40@google.com>

On Fri, Jun 16 2023 at 22:14, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 1b59b2577582f9cf3d0f17245675a76859175cc1
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date:   Thu Jun 1 20:16:34 2023 +0000
>
>     posix-timers: Prevent RT livelock in itimer_delete()
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=106d46e3280000
> start commit:   f7efed9f38f8 Add linux-next specific files for 20230616
> git tree:       linux-next
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=126d46e3280000
> console output: https://syzkaller.appspot.com/x/log.txt?x=146d46e3280000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=60b1a32485a77c16
> dashboard link: https://syzkaller.appspot.com/bug?extid=5fd924f4cd9dc1c7828c
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1401d8ef280000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=176b45cf280000
>
> Reported-by: syzbot+5fd924f4cd9dc1c7828c@syzkaller.appspotmail.com
> Fixes: 1b59b2577582 ("posix-timers: Prevent RT livelock in itimer_delete()")

I've amended the original commit as that is tagged stable.

Thanks for chatching this and reporting!

       tglx

  reply	other threads:[~2023-06-18 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 18:52 [syzbot] [kernel?] possible deadlock in exit_itimers syzbot
2023-06-17  5:14 ` syzbot
2023-06-18 20:44   ` Thomas Gleixner [this message]
     [not found] <20230617074659.4760-1-hdanton@sina.com>
2023-06-17  9:50 ` 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=87v8fkqz4b.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+5fd924f4cd9dc1c7828c@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.