From: Rui Xu <rui.xu@easystack.cn>
To: philipp.reisner@linbit.com, drbd-dev@lists.linbit.com,
joel.colledge@linbit.com
Cc: Rui Xu <rui.xu@easystack.cn>, dongsheng.yang@easystack.cn
Subject: [Drbd-dev] [PATCH v2] drbd: fix a race of drbd_free_peer_req
Date: Tue, 26 Apr 2022 16:09:03 +0800 [thread overview]
Message-ID: <20220426080903.1831211-1-rui.xu@easystack.cn> (raw)
Commit e061feb8 and 9a11ebeb5 introduce a bug to race with drbd_free_peer_req()
in got_peer_ack.
drbd_free_page_chain in drbd_finish_peer_reqs and got_peer_ack may happen
concurrently, the sequence is as follows:
drbd_finish_peer_reqs got_peer_ack
drbd_free_page_chain drbd_free_peer_req
spin_lock()
page_chain_add
spin_unlock() spin_lock()
page_chain_add
spin_unlock()
We can see that page_chain_add will be called twice which will lead
to crash.
Swap drbd_may_finish_epoch() and drbd_free_page_chain() in e_end_block()
to ensure that got_peer_ack will not be called while still processing
the request in drbd_finish_peer_reqs().
Signed-off-by: Rui Xu <rui.xu@easystack.cn>
---
drbd/drbd_receiver.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drbd/drbd_receiver.c b/drbd/drbd_receiver.c
index f077f2b..d0f42d3 100644
--- a/drbd/drbd_receiver.c
+++ b/drbd/drbd_receiver.c
@@ -2560,9 +2560,10 @@ static int e_end_block(struct drbd_work *w, int cancel)
} else
D_ASSERT(device, drbd_interval_empty(&peer_req->i));
+ drbd_free_page_chain(&peer_device->connection->transport, &peer_req->page_chain, 0);
+
drbd_may_finish_epoch(peer_device->connection, peer_req->epoch, EV_PUT + (cancel ? EV_CLEANUP : 0));
- drbd_free_page_chain(&peer_device->connection->transport, &peer_req->page_chain, 0);
return err;
}
--
1.8.3.1
next reply other threads:[~2022-04-26 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 8:09 Rui Xu [this message]
2022-04-28 8:59 ` [Drbd-dev] [PATCH v2] drbd: fix a race of drbd_free_peer_req Joel Colledge
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=20220426080903.1831211-1-rui.xu@easystack.cn \
--to=rui.xu@easystack.cn \
--cc=dongsheng.yang@easystack.cn \
--cc=drbd-dev@lists.linbit.com \
--cc=joel.colledge@linbit.com \
--cc=philipp.reisner@linbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox