From: Jan Kara <jack@suse.cz>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Jan Kara <jack@suse.cz>,
Jeremi Piotrowski <jpiotrowski@linux.microsoft.com>,
Thilo Fromm <t-lo@linux.microsoft.com>,
Ye Bin <yebin10@huawei.com>,
jack@suse.com, tytso@mit.edu, linux-ext4@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [syzbot] possible deadlock in jbd2_journal_lock_updates
Date: Mon, 21 Nov 2022 16:40:48 +0100 [thread overview]
Message-ID: <20221121154048.iccqmx7zajhxh4aq@quack3> (raw)
In-Reply-To: <a98303db-85df-a64d-d672-c16d1e0d8b49@leemhuis.info>
On Mon 21-11-22 16:18:09, Thorsten Leemhuis wrote:
> On 21.11.22 16:00, Jan Kara wrote:
> > OK, attached patch fixes the deadlock for me. Can you test whether it fixes
> > the problem for you as well? Thanks!
>
> Jan, many thx for taking care of this. There is one small thing to
> improve, please add the following tags to your patch:
>
> Link:
> https://lore.kernel.org/r/c77bf00f-4618-7149-56f1-b8d1664b9d07@linux.microsoft.com/
Good point. Thanks, added!
> Not sure, maybe a reported-by for Syzbot would be good as well, see:
> https://lore.kernel.org/linux-ext4/000000000000892a3005e5b5d96c@google.com/
The syzbot report is actually unrelated. So far I think that the bisection
that landed guys on the same commit as syzbot was just luck or maybe change
in timing that made the problem easier to reproduce.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-11-21 15:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 7:34 [syzbot] possible deadlock in jbd2_journal_lock_updates syzbot
2022-08-08 16:38 ` syzbot
2022-08-24 10:06 ` Jan Kara
2022-09-28 7:30 ` Thilo Fromm
2022-09-29 8:27 ` Jan Kara
2022-09-29 13:18 ` Thilo Fromm
2022-10-04 6:38 ` Jeremi Piotrowski
2022-10-04 9:10 ` Jan Kara
2022-10-04 14:21 ` Thilo Fromm
2022-10-05 15:10 ` Jan Kara
2022-10-10 14:24 ` Jeremi Piotrowski
2022-10-14 6:42 ` Thilo Fromm
2022-10-14 13:25 ` Jan Kara
2022-10-21 10:23 ` Thilo Fromm
2022-10-24 10:46 ` Jan Kara
2022-10-24 16:32 ` Thilo Fromm
2022-10-26 10:18 ` Jan Kara
2022-11-10 12:57 ` Jeremi Piotrowski
2022-11-10 15:26 ` Jan Kara
2022-11-10 19:27 ` Jeremi Piotrowski
2022-11-11 14:24 ` Jan Kara
2022-11-11 15:10 ` Jeremi Piotrowski
2022-11-11 15:52 ` Jeremi Piotrowski
2022-11-21 13:35 ` Jan Kara
2022-11-21 15:00 ` Jan Kara
2022-11-21 15:18 ` Thorsten Leemhuis
2022-11-21 15:40 ` Jan Kara [this message]
2022-11-21 18:15 ` Jeremi Piotrowski
2022-11-22 11:57 ` Jan Kara
2022-11-22 17:48 ` Jeremi Piotrowski
2022-11-23 19:41 ` Jan Kara
2022-09-30 12:16 ` [syzbot] possible deadlock in jbd2_journal_lock_updates #forregzbot Thorsten Leemhuis
2022-11-23 9:56 ` Thorsten Leemhuis
2023-04-30 23:38 ` [syzbot] possible deadlock in jbd2_journal_lock_updates Theodore Ts'o
[not found] <20220819122008.1561-1-hdanton@sina.com>
2022-08-19 16:00 ` syzbot
[not found] <20220821023626.1810-1-hdanton@sina.com>
2022-08-21 10:34 ` 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=20221121154048.iccqmx7zajhxh4aq@quack3 \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=jpiotrowski@linux.microsoft.com \
--cc=linux-ext4@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=t-lo@linux.microsoft.com \
--cc=tytso@mit.edu \
--cc=yebin10@huawei.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.