Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 09 4月, 2013 1 次提交
  3. 26 3月, 2013 1 次提交
  5. 29 9月, 2012 2 次提交
  7. 03 8月, 2012 1 次提交
  9. 01 8月, 2012 2 次提交
  11. 31 7月, 2012 1 次提交
  13. 10 5月, 2012 2 次提交
  15. 28 4月, 2012 6 次提交
  17. 11 3月, 2012 2 次提交
  19. 01 2月, 2012 1 次提交
  21. 01 11月, 2011 1 次提交
  23. 31 10月, 2011 1 次提交
  25. 20 7月, 2011 1 次提交
  27. 15 7月, 2011 1 次提交
  29. 13 7月, 2011 2 次提交
  31. 21 6月, 2011 1 次提交
  33. 30 5月, 2011 3 次提交
  35. 27 3月, 2011 1 次提交
    • T
      NFS: Fix a hang in the writeback path · 4d65c520
      由 Trond Myklebust 提交于 
      Now that the inode scalability patches have been merged, it is no longer
safe to call igrab() under the inode->i_lock.
Now that we no longer call nfs_clear_request() until the nfs_page is
being freed, we know that we are always holding a reference to the
nfs_open_context, which again holds a reference to the path, and so
the inode cannot be freed until the last nfs_page has been removed
from the radix tree and freed.

We can therefore skip the igrab()/iput() altogether.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      4d65c520
  37. 24 3月, 2011 1 次提交
    • F
      NFSv4.1: add generic layer hooks for pnfs COMMIT · a861a1e1
      由 Fred Isaman 提交于 
      We create three major hooks for the pnfs code.

pnfs_mark_request_commit() is called during writeback_done from
nfs_mark_request_commit, which gives the driver an opportunity to
claim it wants control over commiting a particular req.

pnfs_choose_commit_list() is called from nfs_scan_list
to choose which list a given req should be added to, based on
where we intend to send it for COMMIT.  It is up to the driver
to have preallocated list headers for each destination it may need.

pnfs_commit_list() is how the driver actually takes control, it is
used instead of nfs_commit_list().

In order to pass information between the above functions, we create
a union in nfs_page to hold a lseg (which is possible because the req is
not on any list while in transition), and add some flags to indicate
if we need to use the pnfs code.
Signed-off-by: NFred Isaman <iisaman@netapp.com>
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      a861a1e1
  39. 22 3月, 2011 1 次提交
  41. 12 3月, 2011 4 次提交
  43. 22 12月, 2010 1 次提交
  45. 08 12月, 2010 1 次提交
    • T
      nfs: remove extraneous and problematic calls to nfs_clear_request · 2df485a7
      由 Trond Myklebust 提交于 
      When a nfs_page is freed, nfs_free_request is called which also calls
nfs_clear_request to clean out the lock and open contexts and free the
pagecache page.

However, a couple of places in the nfs code call nfs_clear_request
themselves. What happens here if the refcount on the request is still high?
We'll be releasing contexts and freeing pointers while the request is
possibly still in use.

Remove those bare calls to nfs_clear_context. That should only be done when
the request is being freed.

Note that when doing this, we need to watch out for tests of req->wb_page.
Previously, nfs_set_page_tag_locked() and nfs_clear_page_tag_locked()
would check the value of req->wb_page to figure out if the page is mapped
into the nfsi->nfs_page_tree. We now indicate the page is mapped using
the new bit PG_MAPPED in req->wb_flags .
Reported-by: NJeff Layton <jlayton@redhat.com>
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      2df485a7
  47. 28 10月, 2010 1 次提交
  49. 31 7月, 2010 1 次提交