linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: hare@suse.de
Cc: Igor Druzhinin <igor.druzhinin@citrix.com>,
	<fcoe-devel@open-fcoe.org>, <linux-scsi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <jejb@linux.ibm.com>,
	<martin.petersen@oracle.com>
Subject: Re: [PATCH RESEND 0/2] Fixing libfc memory leaks
Date: Mon, 20 Jan 2020 23:56:24 -0500	[thread overview]
Message-ID: <yq1pnfdif0n.fsf@oracle.com> (raw)
In-Reply-To: <1579013000-14570-1-git-send-email-igor.druzhinin@citrix.com> (Igor Druzhinin's message of "Tue, 14 Jan 2020 14:43:18 +0000")


Hannes,

> Could you take a look at those?
> At least the first one causes noticeable memory decline over time
> for some of our deployments.
>
> Igor Druzhinin (2):
>   scsi: libfc: free response frame from GPN_ID
>   scsi: libfc: drop extra rport reference in fc_rport_create()
>
>  drivers/scsi/libfc/fc_disc.c  | 2 ++
>  drivers/scsi/libfc/fc_rport.c | 4 +++-
>  2 files changed, 5 insertions(+), 1 deletion(-)

Please review!

-- 
Martin K. Petersen	Oracle Linux Engineering

      parent reply	other threads:[~2020-01-21  4:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 14:43 [PATCH RESEND 0/2] Fixing libfc memory leaks Igor Druzhinin
2020-01-14 14:43 ` [PATCH RESEND 1/2] scsi: libfc: free response frame from GPN_ID Igor Druzhinin
2020-02-21  9:18   ` Hannes Reinecke
2020-02-21 22:56   ` Martin K. Petersen
2020-01-14 14:43 ` [PATCH RESEND 2/2] scsi: libfc: drop extra rport reference in fc_rport_create() Igor Druzhinin
2020-02-21  9:21   ` Hannes Reinecke
2020-01-21  4:56 ` 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=yq1pnfdif0n.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=fcoe-devel@open-fcoe.org \
    --cc=hare@suse.de \
    --cc=igor.druzhinin@citrix.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).