From: Dmitry Bogdanov <d.bogdanov@yadro.com>
To: Martin Petersen <martin.petersen@oracle.com>,
<target-devel@vger.kernel.org>
Cc: <linux-scsi@vger.kernel.org>, <linux@yadro.com>
Subject: Re: [RESEND v2 0/4] target: fix bugs in Persistent Reservations
Date: Fri, 2 Dec 2022 13:37:44 +0300 [thread overview]
Message-ID: <20221202103744.GA15327@yadro.com> (raw)
In-Reply-To: <20221202103331.14297-1-d.bogdanov@yadro.com>
On Fri, Dec 02, 2022 at 01:33:27PM +0300, Dmitry Bogdanov wrote:
> This patch set fixes few rare bugs and deviations from standard in
> PREEMPT AND ABORT and REGISTER AND MOVE operations.
>
> v2:
> remove superfluous parentheses
> fix indentation
>
> Dmitry Bogdanov (4):
> target: core: fix preempt and abort for allreg res
> target: core: fix memory leak in preempt_and_abort
> target: core: abort all preempted regs if requested
> target: core: new key must be used for moved PR
>
> drivers/target/target_core_pr.c | 33 ++++++++++++++++++++++++++-------
> 1 file changed, 26 insertions(+), 7 deletions(-)
>
> --
> 2.25.1
>
Sorry, found it in 6.1.
Thought it was not merged because I did not find it in 6.2/scsi-*
branches.
prev parent reply other threads:[~2022-12-02 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 10:33 [RESEND v2 0/4] target: fix bugs in Persistent Reservations Dmitry Bogdanov
2022-12-02 10:33 ` [RESEND v2 1/4] target: core: fix preempt and abort for allreg res Dmitry Bogdanov
2022-12-02 10:33 ` [RESEND v2 2/4] target: core: fix memory leak in preempt_and_abort Dmitry Bogdanov
2022-12-02 10:33 ` [RESEND v2 3/4] target: core: abort all preempted regs if requested Dmitry Bogdanov
2022-12-02 10:33 ` [RESEND v2 4/4] target: core: new key must be used for moved PR Dmitry Bogdanov
2022-12-02 10:37 ` Dmitry Bogdanov [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=20221202103744.GA15327@yadro.com \
--to=d.bogdanov@yadro.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=martin.petersen@oracle.com \
--cc=target-devel@vger.kernel.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