From: xiubli@redhat.com
To: josef@toxicpanda.com, axboe@kernel.dk, ming.lei@redhat.com
Cc: nbd@other.debian.org, linux-block@vger.kernel.org,
jdillama@redhat.com, mgolub@suse.de, Xiubo Li <xiubli@redhat.com>
Subject: [PATCH v2 0/2] nbd: fix use-after-freed and double lock bugs
Date: Mon, 2 Nov 2020 22:07:56 -0500 [thread overview]
Message-ID: <20201103030758.317781-1-xiubli@redhat.com> (raw)
From: Xiubo Li <xiubli@redhat.com>
Changed in V2:
- fixed possible double lock issue in recv_work().
- adding comments instead to explain why there won't have double lock
issue.
Xiubo Li (2):
nbd: fix use-after-freed crash for nbd->recv_workq
nbd: add comments about double lock for config_lock confusion
drivers/block/nbd.c | 36 +++++++++++++++++++++++++++++++-----
1 file changed, 31 insertions(+), 5 deletions(-)
--
2.18.4
next reply other threads:[~2020-11-03 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 3:07 xiubli [this message]
2020-11-03 3:07 ` [PATCH v2 1/2] nbd: fix use-after-freed crash for nbd->recv_workq xiubli
2020-11-03 4:12 ` Ming Lei
2020-11-03 6:40 ` Xiubo Li
2020-11-03 3:07 ` [PATCH v2 2/2] nbd: add comments about double lock for config_lock confusion xiubli
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=20201103030758.317781-1-xiubli@redhat.com \
--to=xiubli@redhat.com \
--cc=axboe@kernel.dk \
--cc=jdillama@redhat.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=mgolub@suse.de \
--cc=ming.lei@redhat.com \
--cc=nbd@other.debian.org \
/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