Linux NFS development
 help / color / mirror / Atom feed
From: Weston Andros Adamson <dros@monkey.org>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	linux-nfs list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
Date: Fri, 11 Aug 2017 10:18:23 -0400	[thread overview]
Message-ID: <19806192-AF74-4091-BB63-FF41A7687B7F@monkey.org> (raw)
In-Reply-To: <435422355.5999768.1501765030094.JavaMail.zimbra@desy.de>

Hey Tigran,

I don't think so, this fixes a simple memory leak where memory is not =
freed and nothing holds a reference to it. It should not lead to any =
invalid pointers, but will eventually lead to the OOM killer killing a =
bunch of processes.

There have been other recent changes that may have addressed this. Can =
you reproduce with the latest changes?

-dros

> On Aug 3, 2017, at 8:57 AM, Mkrtchyan, Tigran =
<tigran.mkrtchyan@desy.de> wrote:
>=20
> Hi Dros,
>=20
> can this leak be the source of issue described here:  =
http://www.spinics.net/lists/linux-nfs/msg64890.html
>=20
> Tigran.
>=20
> ----- Original Message -----
>> From: "Weston Andros Adamson" <dros@monkey.org>
>> To: "Trond Myklebust" <trond.myklebust@primarydata.com>, "Anna =
Schumaker" <anna.schumaker@netapp.com>
>> Cc: "linux-nfs" <linux-nfs@vger.kernel.org>
>> Sent: Thursday, August 3, 2017 4:07:28 AM
>> Subject: Re: [PATCH] nfs/flexfiles: fix leak of nfs4_ff_ds_version =
arrays
>=20
>> This should probably be CCed to some stable releases too. I'll figure =
it out
>> soon.
>>=20
>> -dros
>>=20
>>> On Aug 1, 2017, at 4:25 PM, Weston Andros Adamson <dros@monkey.org> =
wrote:
>>>=20
>>> The client was freeing the nfs4_ff_layout_ds, but not the contained
>>> nfs4_ff_ds_version array.
>>>=20
>>> Signed-off-by: Weston Andros Adamson <dros@primarydata.com>
>>> ---
>>> fs/nfs/flexfilelayout/flexfilelayoutdev.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>=20
>>> diff --git a/fs/nfs/flexfilelayout/flexfilelayoutdev.c
>>> b/fs/nfs/flexfilelayout/flexfilelayoutdev.c
>>> index 6df7a0cf5660..f32c58bbe556 100644
>>> --- a/fs/nfs/flexfilelayout/flexfilelayoutdev.c
>>> +++ b/fs/nfs/flexfilelayout/flexfilelayoutdev.c
>>> @@ -32,6 +32,7 @@ void nfs4_ff_layout_free_deviceid(struct =
nfs4_ff_layout_ds
>>> *mirror_ds)
>>> {
>>> 	nfs4_print_deviceid(&mirror_ds->id_node.deviceid);
>>> 	nfs4_pnfs_ds_put(mirror_ds->ds);
>>> +	kfree(mirror_ds->ds_versions);
>>> 	kfree_rcu(mirror_ds, id_node.rcu);
>>> }
>>>=20
>>> --
>>> 2.11.0 (Apple Git-81)
>>>=20
>>=20
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2017-08-11 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 20:25 [PATCH] nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays Weston Andros Adamson
2017-08-03  2:07 ` Weston Andros Adamson
2017-08-03 12:57   ` Mkrtchyan, Tigran
2017-08-11 14:18     ` Weston Andros Adamson [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=19806192-AF74-4091-BB63-FF41A7687B7F@monkey.org \
    --to=dros@monkey.org \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.de \
    --cc=trond.myklebust@primarydata.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