From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bodo Stroesser <bostroesser@gmail.com>,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Mike Christie <michael.christie@oracle.com>
Subject: Re: [PATCH 0/2] scsi: target: tcmu: Fix memory leak
Date: Thu, 25 Feb 2021 21:22:06 -0500 [thread overview]
Message-ID: <161430583252.29974.5977995641102362991.b4-ty@oracle.com> (raw)
In-Reply-To: <20210218175039.7829-1-bostroesser@gmail.com>
On Thu, 18 Feb 2021 18:50:37 +0100, Bodo Stroesser wrote:
> This small series applies to Martin's for-next.
>
> This is the third attempt to fix a severe memory leak in tcmu.
> Previous patches:
> https://lore.kernel.org/linux-scsi/20201218141534.9918-1-bostroesser@gmail.com/
> and
> https://lore.kernel.org/linux-scsi/20210210194031.7422-1-bostroesser@gmail.com/
>
> [...]
Applied to 5.12/scsi-queue, thanks!
[1/2] scsi: target: tcmu: Move some functions without code change
https://git.kernel.org/mkp/scsi/c/43bf922cdd62
[2/2] scsi: target: tcmu: Fix memory leak caused by wrong uio usage
https://git.kernel.org/mkp/scsi/c/8f33bb2400f4
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-02-26 2:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 17:50 [PATCH 0/2] scsi: target: tcmu: Fix memory leak Bodo Stroesser
2021-02-18 17:50 ` [PATCH 1/2] scsi: target: tcmu: Move some functions without code change Bodo Stroesser
2021-02-18 17:50 ` [PATCH 2/2] scsi: target: tcmu: Fix memory leak caused by wrong uio usage Bodo Stroesser
2021-02-19 19:01 ` [PATCH 0/2] scsi: target: tcmu: Fix memory leak michael.christie
2021-02-23 3:35 ` Martin K. Petersen
2021-02-26 2:22 ` Martin K. Petersen [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=161430583252.29974.5977995641102362991.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bostroesser@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.christie@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 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.