From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Wenwen Wang <wang6495@umn.edu>
Cc: Wenwen Wang <wenwen@cs.uga.edu>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org (open list:BLOCK LAYER),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH v2] block/bio-integrity: fix a memory leak bug
Date: Thu, 11 Jul 2019 21:10:20 -0400 [thread overview]
Message-ID: <yq1lfx46osj.fsf@oracle.com> (raw)
In-Reply-To: <1562872923-2463-1-git-send-email-wang6495@umn.edu> (Wenwen Wang's message of "Thu, 11 Jul 2019 14:22:02 -0500")
Wenwen,
> To fix this issue, free the allocated buffer before returning from
> bio_integrity_prep().
Acked-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-07-12 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 19:22 [PATCH v2] block/bio-integrity: fix a memory leak bug Wenwen Wang
2019-07-12 0:33 ` Ming Lei
2019-07-12 1:10 ` Martin K. Petersen [this message]
2019-07-12 2:02 ` Jens Axboe
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=yq1lfx46osj.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wang6495@umn.edu \
--cc=wenwen@cs.uga.edu \
/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;
as well as URLs for NNTP newsgroup(s).