From: Chao Yu <yuchao0@huawei.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [f2fs-dev] Fwd: [Bug 208565] There may be dead lock for cp_rwsem during checkpoint
Date: Fri, 17 Jul 2020 14:16:13 +0800 [thread overview]
Message-ID: <25bb20b5-e628-8807-d4ec-d05d77607a69@huawei.com> (raw)
In-Reply-To: <bug-208565-202145-boDe7CCxPJ@https.bugzilla.kernel.org/>
Hi Eric,
Could you please help to test Jaegeak's patch with generic/204 testcase
to see whether there is a regression?
-------- Forwarded Message --------
Subject: [f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint
Date: Fri, 17 Jul 2020 02:26:47 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
https://bugzilla.kernel.org/show_bug.cgi?id=208565
--- Comment #4 from Chao Yu (chao@kernel.org) ---
Passed, we should ask Eric to retest in his enviornment, to make sure there is
actually no regression.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-07-17 6:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:24 [f2fs-dev] [Bug 208565] New: There may be dead lock for cp_rwsem during checkpoint bugzilla-daemon
2020-07-16 17:15 ` [f2fs-dev] [Bug 208565] " bugzilla-daemon
2020-07-24 1:31 ` Chao Yu
2020-07-17 1:54 ` bugzilla-daemon
2020-07-17 2:02 ` bugzilla-daemon
2020-07-17 2:26 ` bugzilla-daemon
2020-07-17 6:16 ` Chao Yu [this message]
2020-07-17 2:47 ` bugzilla-daemon
2020-07-23 7:11 ` bugzilla-daemon
2020-07-24 1:31 ` bugzilla-daemon
2020-07-24 3:21 ` bugzilla-daemon
2020-07-24 3:38 ` Chao Yu
2020-07-24 3:38 ` bugzilla-daemon
2020-07-24 3:56 ` bugzilla-daemon
2020-07-24 6:36 ` bugzilla-daemon
2020-07-24 17:25 ` bugzilla-daemon
2022-09-27 0:48 ` bugzilla-daemon
2022-09-27 0:49 ` bugzilla-daemon
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=25bb20b5-e628-8807-d4ec-d05d77607a69@huawei.com \
--to=yuchao0@huawei.com \
--cc=ebiggers@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.