linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vitaliy Gusev <gusev.vitaliy@nexenta.com>
To: Andy Adamson <andros@netapp.com>
Cc: trond.myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [V2, 1/1] NFSv4.1: remove pnfs_layout_hdr from pnfs_destroy_all_layouts tmp_list
Date: Sun, 15 May 2011 02:50:35 +0400	[thread overview]
Message-ID: <4DCF073B.1060400@nexenta.com> (raw)
In-Reply-To: <1305091198-27378-1-git-send-email-andros@netapp.com>

On 01/-10/-28163 10:59 PM, Andy Adamson wrote:
> From: Andy Adamson<andros@netapp.com>
>
> Prevents an infinite loop as list was never emptied.
>
> Signed-off-by: Andy Adamson<andros@netapp.com>
> +++ b/fs/nfs/pnfs.c
> @@ -383,6 +383,7 @@ pnfs_destroy_all_layouts(struct nfs_client *clp)
>   				plh_layouts);
>   		dprintk("%s freeing layout for inode %lu\n", __func__,
>   			lo->plh_inode->i_ino);
> +		list_del_init(&lo->plh_layouts);
>   		pnfs_destroy_layout(NFS_I(lo->plh_inode));

Shouldn't pnfs_destroy_layout() do it ?

Really see:

   pnfs_destroy_layout(struct nfs_inode *nfsi)
   {
   	struct pnfs_layout_hdr *lo;
   	LIST_HEAD(tmp_list);

   	spin_lock(&nfsi->vfs_inode.i_lock);
   	lo = nfsi->layout;
    ^^^^^^^^^^^^^^^^^^^^
Here is our "lo".


   	if (lo) {
   		lo->plh_block_lgets++; /* permanently block new LAYOUTGETs */
   		mark_matching_lsegs_invalid(lo, &tmp_list, IOMODE_ANY);
   	}
   	spin_unlock(&nfsi->vfs_inode.i_lock);
   	pnfs_free_lseg_list(&tmp_list);
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It does cleanup and deletes lo from the list.


I think really problem is more deeper. I investigated  debug messages:

    [  701.210784] put_lseg: lseg ffff88002cc36108 ref 5721 valid 1
    [  701.463495] pnfs_destroy_all_layouts freeing layout for inode 9
    [  701.465382] mark_matching_lsegs_invalid:Begin lo ffff880031b35ed8
    [  701.467172] mark_matching_lsegs_invalid: freeing lseg 
ffff88002cc36108 iomode 2 offset 0 length 18446744073709551615


    [701.470401] 701.470401] mark_lseg_invalid: lseg ffff88002cc36108 
ref 5720
    [  701.472071] mark_matching_lsegs_invalid:Return 1
    [  701.473623] pnfs_destroy_all_layouts freeing layout for inode 9
    [  701.475302] mark_matching_lsegs_invalid:Begin lo ffff880031b35ed8
    [  701.476981] mark_matching_lsegs_invalid: freeing lseg 
ffff88002cc36108 iomode 2 offset 0 length 18446744073709551615
    [  701.480549] mark_matching_lsegs_invalid:Return 1


    [  701.482136] pnfs_destroy_all_layouts freeing layout for inode 9
    [  701.483802] mark_matching_lsegs_invalid:Begin lo ffff880031b35ed8
    [  701.485461] mark_matching_lsegs_invalid: freeing lseg 
ffff88002cc36108 iomode 2 offset 0 length 18446744073709551615
    [  701.488598] mark_matching_lsegs_invalid:Return 1   ...


"Return 1" shows that mark_lseg_invalid() didn't do anything, because at 
first call it mark segment as invalid.

Also you can see that segment ref counter for last put_lseg() is 5720. I 
suppose that leak of refconter is real reason of the inifinite loop.


---
Thanks,
Vitaliy Gusev

  reply	other threads:[~2011-05-14 23:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11  5:19 [PATCH V2 1/1] NFSv4.1: remove pnfs_layout_hdr from pnfs_destroy_all_layouts tmp_list andros
2011-05-14 22:50 ` Vitaliy Gusev [this message]
2011-05-16 17:44   ` [V2, " Andy Adamson
2011-05-16 19:39     ` Vitaliy Gusev
2011-05-17 15:29       ` Andy Adamson

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=4DCF073B.1060400@nexenta.com \
    --to=gusev.vitaliy@nexenta.com \
    --cc=andros@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@netapp.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;
as well as URLs for NNTP newsgroup(s).