[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241023094553epcms2p1c4b830a99a1f6b10cba8fd9bbcd8e2ac@epcms2p1>
Date: Wed, 23 Oct 2024 18:45:53 +0900
From: Daejun Park <daejun7.park@...sung.com>
To: "chao@...nel.org" <chao@...nel.org>, "jaegeuk@...nel.org"
<jaegeuk@...nel.org>
CC: "syzbot+be4a9983e95a5e25c8d3@...kaller.appspotmail.com"
<syzbot+be4a9983e95a5e25c8d3@...kaller.appspotmail.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-f2fs-devel@...ts.sourceforge.net"
<linux-f2fs-devel@...ts.sourceforge.net>, Daejun Park
<daejun7.park@...sung.com>
Subject: RE: [f2fs-dev] [PATCH v2] f2fs: fix to avoid potential deadlock in
f2fs_record_stop_reason()
Hi Chao Yu,
> ...
>
> Let's always create an asynchronous task in f2fs_handle_critical_error()
> rather than calling f2fs_record_stop_reason() synchronously to avoid
> this potential deadlock issue.
>
> Fixes: b62e71be2110 ("f2fs: support errors=remount-rocontinuepanic mountoption")
> Reported-by: syzbot+be4a9983e95a5e25c8d3@...kaller.appspotmail.com
> Closes: https://lore.kernel.org/all/6704d667.050a0220.1e4d62.0081.GAE@google.com
> Signed-off-by: Chao Yu <chao@...nel.org>
Reviewed-by: Daejun Park <daejun7.park@...sung.com>
Powered by blists - more mailing lists