1. 14 7月, 2012 6 次提交
    • A
      stop passing nameidata * to ->d_revalidate() · 0b728e19
      Al Viro 提交于
      Just the lookup flags.  Die, bastard, die...
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      0b728e19
    • A
      kill struct opendata · 30d90494
      Al Viro 提交于
      Just pass struct file *.  Methods are happier that way...
      There's no need to return struct file * from finish_open() now,
      so let it return int.  Next: saner prototypes for parts in
      namei.c
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      30d90494
    • A
      make ->atomic_open() return int · d9585277
      Al Viro 提交于
      Change of calling conventions:
      old		new
      NULL		1
      file		0
      ERR_PTR(-ve)	-ve
      
      Caller *knows* that struct file *; no need to return it.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      d9585277
    • A
      ->atomic_open() prototype change - pass int * instead of bool * · 47237687
      Al Viro 提交于
      ... and let finish_open() report having opened the file via that sucker.
      Next step: don't modify od->filp at all.
      
      [AV: FILE_CREATE was already used by cifs; Miklos' fix folded]
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      47237687
    • M
      vfs: add i_op->atomic_open() · d18e9008
      Miklos Szeredi 提交于
      Add a new inode operation which is called on the last component of an open.
      Using this the filesystem can look up, possibly create and open the file in one
      atomic operation.  If it cannot perform this (e.g. the file type turned out to
      be wrong) it may signal this by returning NULL instead of an open struct file
      pointer.
      
      i_op->atomic_open() is only called if the last component is negative or needs
      lookup.  Handling cached positive dentries here doesn't add much value: these
      can be opened using f_op->open().  If the cached file turns out to be invalid,
      the open can be retried, this time using ->atomic_open() with a fresh dentry.
      
      For now leave the old way of using open intents in lookup and revalidate in
      place.  This will be removed once all the users are converted.
      
      David Howells noticed that if ->atomic_open() opens the file but does not create
      it, handle_truncate() will be called on it even if it is not a regular file.
      Fix this by checking the file type in this case too.
      Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      d18e9008
    • A
      vfs: update documentation on ->i_dentry handling · 049b3c10
      Al Viro 提交于
      we used to need to clean it in RCU callback freeing an inode;
      in 3.2 that requirement went away.  Unfortunately, it hadn't
      been reflected in Documentation/filesystems/porting.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      049b3c10
  2. 07 7月, 2012 2 次提交
  3. 06 7月, 2012 1 次提交
  4. 03 7月, 2012 3 次提交
  5. 26 6月, 2012 1 次提交
    • M
      stable: Allow merging of backports for serious user-visible performance issues · eb3979f6
      Mel Gorman 提交于
      Distribution kernel maintainers routinely backport fixes for users that
      were deemed important but not "something critical" as defined by the
      rules. To users of these kernels they are very serious and failing to fix
      them reduces the value of -stable.
      
      The problem is that the patches fixing these issues are often subtle and
      prone to regressions in other ways and need greater care and attention.
      To combat this, these "serious" backports should have a higher barrier
      to entry.
      
      This patch relaxes the rules to allow a distribution maintainer to merge
      to -stable a backported patch or small series that fixes a "serious"
      user-visible performance issue. They should include additional information on
      the user-visible bug affected and a link to the bugzilla entry if available.
      The same rules about the patch being already in mainline still apply.
      Signed-off-by: NMel Gorman <mgorman@suse.de>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      eb3979f6
  6. 21 6月, 2012 1 次提交
  7. 19 6月, 2012 1 次提交
  8. 18 6月, 2012 3 次提交
  9. 14 6月, 2012 6 次提交
  10. 12 6月, 2012 3 次提交
  11. 07 6月, 2012 1 次提交
  12. 05 6月, 2012 2 次提交
  13. 04 6月, 2012 1 次提交
  14. 03 6月, 2012 1 次提交
    • J
      dm thin: provide userspace access to pool metadata · cc8394d8
      Joe Thornber 提交于
      This patch implements two new messages that can be sent to the thin
      pool target allowing it to take a snapshot of the _metadata_.  This,
      read-only snapshot can be accessed by userland, concurrently with the
      live target.
      
      Only one metadata snapshot can be held at a time.  The pool's status
      line will give the block location for the current msnap.
      
      Since version 0.1.5 of the userland thin provisioning tools, the
      thin_dump program displays the msnap as follows:
      
          thin_dump -m <msnap root> <metadata dev>
      
      Available here: https://github.com/jthornber/thin-provisioning-tools
      
      Now that userland can access the metadata we can do various things
      that have traditionally been kernel side tasks:
      
           i) Incremental backups.
      
           By using metadata snapshots we can work out what blocks have
           changed over time.  Combined with data snapshots we can ensure
           the data doesn't change while we back it up.
      
           A short proof of concept script can be found here:
      
           https://github.com/jthornber/thinp-test-suite/blob/master/incremental_backup_example.rb
      
           ii) Migration of thin devices from one pool to another.
      
           iii) Merging snapshots back into an external origin.
      
           iv) Asyncronous replication.
      Signed-off-by: NJoe Thornber <ejt@redhat.com>
      Signed-off-by: NAlasdair G Kergon <agk@redhat.com>
      cc8394d8
  15. 02 6月, 2012 2 次提交
    • M
      x86, efi: Add EFI boot stub documentation · 0c759662
      Matt Fleming 提交于
      Since we can't expect every user to read the EFI boot stub code it
      seems prudent to have a couple of paragraphs explaining what it is and
      how it works.
      
      The "initrd=" option in particular is tricky because it only
      understands absolute EFI-style paths (backslashes as directory
      separators), and until now this hasn't been documented anywhere. This
      has tripped up a couple of users.
      
      Cc: Matthew Garrett <mjg@redhat.com>
      Cc: Randy Dunlap <rdunlap@xenotime.net>
      Signed-off-by: NMatt Fleming <matt.fleming@intel.com>
      Link: http://lkml.kernel.org/r/1331907517-3985-4-git-send-email-matt@console-pimps.orgSigned-off-by: NH. Peter Anvin <hpa@zytor.com>
      0c759662
    • J
      fs: introduce inode operation ->update_time · c3b2da31
      Josef Bacik 提交于
      Btrfs has to make sure we have space to allocate new blocks in order to modify
      the inode, so updating time can fail.  We've gotten around this by having our
      own file_update_time but this is kind of a pain, and Christoph has indicated he
      would like to make xfs do something different with atime updates.  So introduce
      ->update_time, where we will deal with i_version an a/m/c time updates and
      indicate which changes need to be made.  The normal version just does what it
      has always done, updates the time and marks the inode dirty, and then
      filesystems can choose to do something different.
      
      I've gone through all of the users of file_update_time and made them check for
      errors with the exception of the fault code since it's complicated and I wasn't
      quite sure what to do there, also Jan is going to be pushing the file time
      updates into page_mkwrite for those who have it so that should satisfy btrfs and
      make it not a big deal to check the file_update_time() return code in the
      generic fault path. Thanks,
      Signed-off-by: NJosef Bacik <josef@redhat.com>
      c3b2da31
  16. 01 6月, 2012 5 次提交
  17. 31 5月, 2012 1 次提交
反馈
建议
客服 返回
顶部