Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 10 12月, 2014 5 次提交
  3. 02 12月, 2014 1 次提交
  5. 26 11月, 2014 4 次提交
  7. 25 11月, 2014 9 次提交
  9. 20 11月, 2014 11 次提交
    • M
      ovl: ovl_dir_fsync() cleanup · 7676895f
      由 Miklos Szeredi 提交于 
      Check against !OVL_PATH_LOWER instead of OVL_PATH_MERGE.  For a copied up
directory the two are currently equivalent.
Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      7676895f
    • M
      ovl: pass dentry into ovl_dir_read_merged() · c9f00fdb
      由 Miklos Szeredi 提交于 
      Pass dentry into ovl_dir_read_merged() insted of upperpath and lowerpath.
This cleans up callers and paves the way for multi-layer directory reads.
Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      c9f00fdb
    • M
      ovl: use lockless_dereference() for upperdentry · 71d50928
      由 Miklos Szeredi 提交于 
      Don't open code lockless_dereference() in ovl_upperdentry_dereference().
Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      71d50928
    • M
      ovl: allow filenames with comma · 91c77947
      由 Miklos Szeredi 提交于 
      Allow option separator (comma) to be escaped with backslash.
Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      91c77947
    • M
      ovl: fix race in private xattr checks · 52148463
      由 Miklos Szeredi 提交于 
      Xattr operations can race with copy up.  This does not matter as long as
we consistently fiter out "trunsted.overlay.opaque" attribute on upper
directories.

Previously we checked parent against OVL_PATH_MERGE.  This is too general,
and prone to race with copy-up.  I.e. we found the parent to be on the
lower layer but ovl_dentry_real() would return the copied-up dentry,
possibly with the "opaque" attribute.

So instead use ovl_path_real() and decide to filter the attributes based on
the actual type of the dentry we'll use.
Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      52148463
    • M
      ovl: fix remove/copy-up race · a105d685
      由 Miklos Szeredi 提交于 
      ovl_remove_and_whiteout() needs to check if upper dentry exists or not
after having locked upper parent directory.

Previously we used a "type" value computed before locking the upper parent
directory, which is susceptible to racing with copy-up.

There's a similar check in ovl_check_empty_and_clear().  This one is not
actually racy, since copy-up doesn't change the "emptyness" property of a
directory.  Add a comment to this effect, and check the existence of upper
dentry locally to make the code cleaner.
Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      a105d685
    • M
      ovl: rename filesystem type to "overlay" · ef94b186
      由 Miklos Szeredi 提交于 
      Some distributions carry an "old" format of overlayfs while mainline has a
"new" format.

The distros will possibly want to keep the old overlayfs alongside the new
for compatibility reasons.

To make it possible to differentiate the two versions change the name of
the new one from "overlayfs" to "overlay".
Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
Reported-by: NSerge Hallyn <serge.hallyn@ubuntu.com>
Cc: Andy Whitcroft <apw@canonical.com>
      ef94b186
    • C
      btrfs: fix lockups from btrfs_clear_path_blocking · f82c458a
      由 Chris Mason 提交于 
      The fair reader/writer locks mean that btrfs_clear_path_blocking needs
to strictly follow lock ordering rules even when we already have
blocking locks on a given path.

Before we can clear a blocking lock on the path, we need to make sure
all of the locks have been converted to blocking.  This will remove lock
inversions against anyone spinning in write_lock() against the buffers
we're trying to get read locks on.  These inversions didn't exist before
the fair read/writer locks, but now we need to be more careful.

We papered over this deadlock in the past by changing
btrfs_try_read_lock() to be a true trylock against both the spinlock and
the blocking lock.  This was slower, and not sufficient to fix all the
deadlocks.  This patch adds a btrfs_tree_read_lock_atomic(), which
basically means get the spinlock but trylock on the blocking lock.
Signed-off-by: NChris Mason <clm@fb.com>
Signed-off-by: NJosef Bacik <jbacik@fb.com>
Reported-by: NPatrick Schmid <schmid@phys.ethz.ch>
cc: stable@vger.kernel.org #v3.15+
      f82c458a
    • A
      isofs: avoid unused function warning · 7ca2f234
      由 Arnd Bergmann 提交于 
      With the isofs_hash() function removed, isofs_hash_ms() is the only user
of isofs_hash_common(), but it's defined inside of an #ifdef, which triggers
this gcc warning in ARM axm55xx_defconfig starting with v3.18-rc3:

fs/isofs/inode.c:177:1: warning: 'isofs_hash_common' defined but not used [-Wunused-function]

This patch moves the function inside of the same #ifdef section to avoid that
warning, which seems the best compromise of a relatively harmless patch for
a late -rc.
Signed-off-by: NArnd Bergmann <arnd@arndb.de>
Fixes: b0afd8e5 ("isofs: don't bother with ->d_op for normal case")
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      7ca2f234
    • Y
      vfs: fix reference leak in d_prune_aliases() · 4a7795d3
      由 Yan, Zheng 提交于 
      In "d_prune_alias(): just lock the parent and call __dentry_kill()" the old
dget + d_drop + dput has been replaced with lock_parent + __dentry_kill;
unfortunately, dput() does more than just killing dentry - it also drops the
reference to parent.  New variant leaks that reference and needs dput(parent)
after killing the child off.
Signed-off-by: NYan, Zheng <zyan@redhat.com>
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      4a7795d3
    • C
      nfsd: correctly define v4.2 support attributes · 6d0ba043
      由 Christoph Hellwig 提交于 
      Even when security labels are disabled we support at least the same
attributes as v4.1.
Signed-off-by: NChristoph Hellwig <hch@lst.de>
Cc: stable@kernel.org
Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      6d0ba043
  11. 14 11月, 2014 2 次提交
  13. 13 11月, 2014 8 次提交