From: Jens Axboe <axboe@kernel.dk>
To: ming.lei@redhat.com, ZiyangZhang@linux.alibaba.com
Cc: joseph.qi@linux.alibaba.com, linux-block@vger.kernel.org,
xiaoguang.wang@linux.alibaba.com
Subject: Re: [PATCH V2 0/3] ublk_drv: cleanup and bugfix
Date: Tue, 16 Aug 2022 06:16:36 -0600 [thread overview]
Message-ID: <166065219672.192972.12166477403979227046.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220815023633.259825-1-ZiyangZhang@linux.alibaba.com>
On Mon, 15 Aug 2022 10:36:30 +0800, ZiyangZhang wrote:
> The following 3 patches are cleanup and bugfix. Patch 1 and 2
> simply inline a function and update comments for ublk_drv's
> aborting machemism.
>
> Patch 3 fix a null-deref bug reported by myself. Ming gives out a
> patch and I integrate it with more comments on this bug.
>
> [...]
Applied, thanks!
[1/3] ublk_drv: check ubq_daemon_is_dying() in __ublk_rq_task_work()
commit: 966120b51a245c9ff5857c5b169310c248e0ae87
[2/3] ublk_drv: update comment for __ublk_fail_req()
commit: bb24174754afc5a7d185ca5406dcfbc608cdf157
[3/3] ublk_drv: do not add a re-issued request aborted previously to ioucmd's task_work
commit: e6190dd0031d335c22586d34ef898301ed20f230
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-08-16 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 2:36 [PATCH V2 0/3] ublk_drv: cleanup and bugfix ZiyangZhang
2022-08-15 2:36 ` [PATCH V2 1/3] ublk_drv: check ubq_daemon_is_dying() in __ublk_rq_task_work() ZiyangZhang
2022-08-15 2:36 ` [PATCH V2 2/3] ublk_drv: update comment for __ublk_fail_req() ZiyangZhang
2022-08-16 3:01 ` Ming Lei
2022-08-15 2:36 ` [PATCH V2 3/3] ublk_drv: do not add a re-issued request aborted previously to ioucmd's task_work ZiyangZhang
2022-08-16 3:02 ` Ming Lei
2022-08-16 12:16 ` Jens Axboe [this message]
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=166065219672.192972.12166477403979227046.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=ZiyangZhang@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=xiaoguang.wang@linux.alibaba.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