linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Brandenburg <martin@omnibond.com>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [PATCH] orangefs: getattr work (was: Re: Orangefs, v4.5 and the merge window...)
Date: Thu, 17 Mar 2016 16:45:02 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSO.2.20.1603171635400.14887@server1.sysblue.org> (raw)
In-Reply-To: <alpine.OSX.2.20.11.1603151242260.703@mbmbp.mkb.name>

Mike,

The following changes since commit 2f83ace37181e445cab83d1d2a3a1dc88a36a814:

  orangefs: put register_chrdev immediately before register_filesystem (2016-03-17 14:34:10 -0400)

are available in the git repository at:

  https://github.com/martinbrandenburg/linux.git getattr

for you to fetch changes up to 6f0d78264c5c4e0e9da8f98e60da82f87b4a5a99:

  orangefs: remove wrapper around mutex_lock(&inode->i_mutex) (2016-03-17 16:33:08 -0400)

----------------------------------------------------------------
Martin Brandenburg (8):
      orangefs: remove inode->i_lock wrapper
      orangefs: rename orangefs_inode_getattr to orangefs_inode_old_getattr
      orangefs: use new orangefs_inode_getattr to create new inodes
      orangefs: use new orangefs_inode_getattr to get size in write and llseek
      orangefs: use new getattr in inode getattr and permission
      orangefs: add orangefs_inode_check_changed
      orangefs: refactor inode type or link_target change detection
      orangefs: remove wrapper around mutex_lock(&inode->i_mutex)

 fs/orangefs/dcache.c          |   3 +-
 fs/orangefs/file.c            |  13 +-
 fs/orangefs/inode.c           |  19 +-
 fs/orangefs/orangefs-kernel.h |  15 +-
 fs/orangefs/orangefs-utils.c  | 400 ++++++++++++-----------------------------
 5 files changed, 133 insertions(+), 317 deletions(-)

I hope this cleans up getattr significantly and fixes several
outstanding bugs. It is tested rather lightly as we have discussed.

-- Martin

      reply	other threads:[~2016-03-17 20:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 20:18 Orangefs, v4.5 and the merge window Mike Marshall
2016-03-11 21:47 ` Al Viro
2016-03-11 22:35   ` Mike Marshall
2016-03-14 21:03     ` Mike Marshall
2016-03-26  0:21       ` Al Viro
2016-03-26  1:00         ` Mike Marshall
     [not found]         ` <CA+55aFzLC_pdj_ds82YYab5D7jpYMj26s0Frofxxhk=j7SqnjA@mail.gmail.com>
2016-03-26  1:01           ` Al Viro
2016-03-26  1:07             ` Mike Marshall
     [not found]             ` <CA+55aFysWS9mP+QgfAR6LZpEbkp61MUPQu0zDoq7cafmr3M8SA@mail.gmail.com>
2016-03-26  3:55               ` Mike Marshall
2016-03-26  4:30                 ` Al Viro
2016-03-26 12:07                   ` Mike Marshall
2016-03-26 14:47                     ` Al Viro
2016-03-26 15:34                       ` Mike Marshall
2016-03-26 15:50                         ` Al Viro
2016-03-26 17:36                           ` Mike Marshall
2016-03-26 18:28                             ` Al Viro
2016-03-26 18:37                               ` Al Viro
2016-03-26 19:00                                 ` Mike Marshall
2016-03-26 19:51                                   ` Linus Torvalds
2016-03-26 20:47                                     ` Mike Marshall
2016-03-26 21:00                                       ` Linus Torvalds
2016-03-26  1:02           ` Mike Marshall
2016-03-15  4:04   ` Martin Brandenburg
2016-03-15 16:45     ` Martin Brandenburg
2016-03-17 20:45       ` Martin Brandenburg [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=alpine.BSO.2.20.1603171635400.14887@server1.sysblue.org \
    --to=martin@omnibond.com \
    --cc=hubcap@omnibond.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).