public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] vfs part 2
Date: Fri, 5 Mar 2010 16:29:08 +0000	[thread overview]
Message-ID: <20100305162907.GW30031@ZenIV.linux.org.uk> (raw)

	Next part of VFS stuff: getting do_filp_open() to relative
sanity.  There will be more piles (the next one is dealing with
write_inode mess, in an hour or so).  Please, pull from 
git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ for-linus

Shortlog:
Al Viro (18):
      beginning to untangle do_filp_open()
      gut do_filp_open() a bit more (do_last separation)
      Shift releasing nd->root from do_last() to its caller
      unroll do_last: loop in do_filp_open()
      postpone __putname() until after do_last()
      pull the common predecessors into do_last()
      bail out with ELOOP earlier in do_link loop
      pull more into do_last()
      Don't pass mangled open_flag to finish_open()
      Get rid of passing mangled flag to do_last()
      Leave mangled flag only for setting nd.intent.open.flag
      Pull handling of LAST_BIND into do_last(), clean up ok: part in do_filp_open()
      Kill is_link argument of do_last()
      Unify exits in O_CREAT handling
      Turn do_link spaghetty into a normal loop
      Finish pulling of -ESTALE handling to upper level in do_filp_open()
      Get rid of symlink body copying
      Switch !O_CREAT case to use of do_last()

Diffstat:
 fs/namei.c |  523 ++++++++++++++++++++++++++++++------------------------------
 1 files changed, 263 insertions(+), 260 deletions(-)

             reply	other threads:[~2010-03-05 16:29 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 16:29 Al Viro [this message]
2010-03-05 19:53 ` [git pull] vfs part 2 Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2012-03-31  5:19 Al Viro
2012-03-31 18:28 ` Linus Torvalds
2012-03-31 18:31   ` Linus Torvalds
2012-03-31 18:57     ` Al Viro
2012-03-31 19:29       ` Linus Torvalds
2012-03-31 19:39         ` Al Viro
2012-03-31 19:42           ` Al Viro
2012-03-31 19:48           ` Linus Torvalds
2012-03-31 20:08             ` Al Viro
2012-03-31 21:37               ` Linus Torvalds
2015-04-15 18:14 Al Viro
2015-04-23 10:16 ` Andrey Ryabinin
2015-05-25  8:30   ` Andrey Ryabinin
2015-06-21 21:12   ` Al Viro
2015-06-21 21:16     ` Linus Torvalds
2015-06-21 21:35       ` Al Viro
2015-06-22 12:02     ` Andrey Ryabinin
2015-07-01  6:27       ` Al Viro
2015-07-01  7:50         ` Andrey Ryabinin
2015-07-01  8:27           ` Al Viro
2015-07-01  8:41             ` Andrey Ryabinin
2015-07-01  8:55               ` Al Viro
2015-07-01 11:25                 ` Andrey Ryabinin
2015-07-01 18:44                   ` Al Viro
2015-07-02  3:20                     ` Al Viro
2015-07-02 12:00                       ` Jeff Layton
2015-07-02 12:07                         ` Jeff Layton
2015-07-02 16:45                           ` Al Viro
2015-07-02 17:01                             ` Jeff Layton
2015-07-02 17:56                               ` Dominique Martinet
2015-07-02 18:43                                 ` Al Viro
2015-07-02 21:00                                   ` Dominique Martinet
2015-07-02 18:59                                 ` Jeff Layton
2015-07-02 20:36                                 ` Andrey Ryabinin
2015-07-02 18:40                               ` Al Viro
2015-07-02 19:16                                 ` Linus Torvalds
2015-07-02 20:44                                   ` Al Viro

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=20100305162907.GW30031@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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