on the target if:
- the root or admin is asking for it
- the process has write access
- the owner of the file is asking for the dedupe
- the process could get write access
That way users can open read-only and still get dedupe.
Signed-off-by: Mark Fasheh
---
fs/read_write.c | 16
inode_permission check as suggested by Adam Borowski
- V1 discussion: https://marc.info/?l=linux-xfs=152606684017965=2
From: Mark Fasheh
[PATCH] ioctl_fideduperange.2: clarify permission requirements
dedupe permission checks were recently relaxed - update our man page to
reflect those changes.
Signed
Right now we return EINVAL if a process does not have permission to dedupe a
file. This was an oversight on my part. EPERM gives a true description of
the nature of our error, and EINVAL is already used for the case that the
filesystem does not support dedupe.
Signed-off-by: Mark Fasheh
Reviewed
Right now we return EINVAL if a process does not have permission to dedupe a
file. This was an oversight on my part. EPERM gives a true description of
the nature of our error, and EINVAL is already used for the case that the
filesystem does not support dedupe.
Signed-off-by: Mark Fasheh
Reviewed
on the target if:
- the root or admin is asking for it
- the process has write access
- the owner of the file is asking for the dedupe
- the process could get write access
That way users can open read-only and still get dedupe.
Signed-off-by: Mark Fasheh
Acked-by: Darrick J. Wong
---
fs/read_write.c
as suggested by Adam Borowski
- V1 discussion: https://marc.info/?l=linux-xfs=152606684017965=2
From: Mark Fasheh
[PATCH] ioctl_fideduperange.2: clarify permission requirements
dedupe permission checks were recently relaxed - update our man page to
reflect those changes.
Signed-off-by: Mark Fasheh
Right now we return EINVAL if a process does not have permission to dedupe a
file. This was an oversight on my part. EPERM gives a true description of
the nature of our error, and EINVAL is already used for the case that the
filesystem does not support dedupe.
Signed-off-by: Mark Fasheh
Reviewed
inode_permission check as suggested by Adam Borowski
- V1 discussion: https://marc.info/?l=linux-xfs=152606684017965=2
From: Mark Fasheh
[PATCH] ioctl_fideduperange.2: clarify permission requirements
dedupe permission checks were recently relaxed - update our man page to
reflect those changes.
Signed
on the target if:
- the root or admin is asking for it
- the process has write access
- the owner of the file is asking for the dedupe
- the process could get write access
That way users can open read-only and still get dedupe.
Signed-off-by: Mark Fasheh
Acked-by: Darrick J. Wong
---
fs/read_write.c
Hi Al,
On Thu, Aug 02, 2018 at 01:43:48AM +0100, Al Viro wrote:
> On Tue, Jul 31, 2018 at 10:51:57PM +0000, Mark Fasheh wrote:
> > Hi Al,
> >
> > On Tue, Jul 31, 2018 at 11:16:05PM +0100, Al Viro wrote:
> > > On Tue, Jul 31, 2018 at 02:10:43PM -0700, Mark Fasheh
Hi Jeff,
On Wed, Aug 01, 2018 at 07:03:54AM -0400, Jeff Layton wrote:
> On Tue, 2018-07-31 at 14:10 -0700, Mark Fasheh wrote:
> > /proc/locks does not always print the correct inode number/device pair.
> > Update lock_get_status() to use vfs_map_unique_ino_dev() to get the real,
&g
On Wed, Aug 01, 2018 at 08:37:31AM +0300, Amir Goldstein wrote:
> > if (inode) {
> > + __u64 ino;
> > + dev_t dev;
> > +
> > + vfs_map_unique_ino_dev(dentry, , );
> > /* userspace relies on this representation of dev_t */
> >
Hi Amir,
On Wed, Aug 01, 2018 at 08:41:14AM +0300, Amir Goldstein wrote:
> > +void vfs_map_unique_ino_dev(struct dentry *dentry, u64 *ino, dev_t *dev)
>
> I find this function name a bit more than function can guaranty.
> It's just a fancy wrapper around ->getattr()
> How about vfs_get_ino_dev()
On Tue, Jul 31, 2018 at 02:10:42PM -0700, Mark Fasheh wrote:
> diff --git a/fs/stat.c b/fs/stat.c
> index f8e6fb2c3657..80ea42505219 100644
> --- a/fs/stat.c
> +++ b/fs/stat.c
> @@ -84,6 +84,29 @@ int vfs_getattr_nosec(const struct path *path, struct
> kstat *stat,
>
Hi Al,
On Tue, Jul 31, 2018 at 11:16:05PM +0100, Al Viro wrote:
> On Tue, Jul 31, 2018 at 02:10:43PM -0700, Mark Fasheh wrote:
> > ->getattr from inside the kernel won't always have a vfsmount, check for
> > this.
>
> Really? Where would that happen?
It happens in m
an fix this by adding a helper function, vfs_map_unique_ino_dev(), which
will query the owning filesystem (via ->getattr) to get the correct ino/dev
pair. Later patches will update those places which simply dump inode->i_ino
and super->s_dev to use the helper.
Signed-off-by: Mark Fasheh
->getattr from inside the kernel won't always have a vfsmount, check for
this.
Signed-off-by: Mark Fasheh
---
fs/nfs/inode.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
index b65aee481d13..7a3d90a7cc92 100644
--- a/fs/nfs/inod
/proc/locks does not always print the correct inode number/device pair.
Update lock_get_status() to use vfs_map_unique_ino_dev() to get the real,
unique values for userspace.
Signed-off-by: Mark Fasheh
---
fs/locks.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git
Hi,
These patches are follow-up to this conversation on fsdevel which provides a
good break-down of the core problem:
https://www.spinics.net/lists/linux-fsdevel/msg128003.html
That e-mail was in turn a follow-up to the following patch series:
https://lwn.net/Articles/753917/
which tried to
). We
can fix this by using vfs_map_unique_ino_dev() to map the unique ino/dev
pair for us.
Signed-off-by: Mark Fasheh
---
fs/proc/nommu.c | 11 ---
fs/proc/task_mmu.c | 8 +++-
fs/proc/task_nommu.c | 8 +++-
3 files changed, 10 insertions(+), 17 deletions(-)
diff --git
On Tue, Jul 17, 2018 at 12:48:18PM -0700, Darrick J. Wong wrote:
> On Tue, Jul 17, 2018 at 12:09:04PM -0700, Mark Fasheh wrote:
> > Hi Al,
> >
> > The following patches fix a couple of issues with the permission check
> > we do in vfs_dedupe_file_range(). I sent t
On Tue, Jul 17, 2018 at 12:48:18PM -0700, Darrick J. Wong wrote:
> On Tue, Jul 17, 2018 at 12:09:04PM -0700, Mark Fasheh wrote:
> > From: Mark Fasheh
> >
> > [PATCH] ioctl_fideduperange.2: clarify permission requirements
> >
> > dedupe permission checks were
on the target if:
- the root or admin is asking for it
- the process has write access
- the owner of the file is asking for the dedupe
- the process could get write access
That way users can open read-only and still get dedupe.
Signed-off-by: Mark Fasheh
Acked-by: Darrick J. Wong
---
fs/read_write.c
Right now we return EINVAL if a process does not have permission to dedupe a
file. This was an oversight on my part. EPERM gives a true description of
the nature of our error, and EINVAL is already used for the case that the
filesystem does not support dedupe.
Signed-off-by: Mark Fasheh
Reviewed
to V3:
- Return bool from allow_file_dedupe
- V2 discussion: https://www.spinics.net/lists/linux-btrfs/msg78421.html
Changes from V1 to V2:
- Add inode_permission check as suggested by Adam Borowski
- V1 discussion: https://marc.info/?l=linux-xfs=152606684017965=2
From: Mark Fasheh
[PATCH
On Thu, Jun 07, 2018 at 10:38:51AM +0300, Amir Goldstein wrote:
> On Thu, Jun 7, 2018 at 12:38 AM, Mark Fasheh wrote:
> > Hi,
> >
> > We have an inconsistency in how the kernel is exporting inode number /
> > device pairs for user space. There's of course stat(2) and s
Hi Darrick,
On Thu, Jun 07, 2018 at 11:17:51AM -0700, Darrick J. Wong wrote:
> Looks ok, but could you please update the manpage for
> ioctl_fideduperange to elaborate on when userspace can expect EPERM?
>
> Acked-by: Darrick J. Wong
Yes, good idea. I can handle that.
Thanks,
--Mark
Right now we return EINVAL if a process does not have permission to dedupe a
file. This was an oversight on my part. EPERM gives a true description of
the nature of our error, and EINVAL is already used for the case that the
filesystem does not support dedupe.
Signed-off-by: Mark Fasheh
Reviewed
Hi Al,
The following patches fix a couple of issues with the permission check
we do in vfs_dedupe_file_range(). I sent them out for review twice, a
changelog is attached. If they look ok to you, I'd appreciate them
being pushed upstream.
You can get them from git if you like:
git pull
on the target if:
- the root or admin is asking for it
- the process has write access
- the owner of the file is asking for the dedupe
- the process could get write access
That way users can open read-only and still get dedupe.
Signed-off-by: Mark Fasheh
---
fs/read_write.c | 17 +++--
1
Hi Ian,
On Thu, Jun 07, 2018 at 08:47:28AM +0800, Ian Kent wrote:
> On Wed, 2018-06-06 at 23:38 +0200, Mark Fasheh wrote:
> > Hi,
>
> I'm not sure I understand what the problem is.
I'll try to elaborate below.
> > We have an inconsistency in how the kernel is e
Hi,
We have an inconsistency in how the kernel is exporting inode number /
device pairs for user space. There's of course stat(2) and statx(2),
but aside from those we simply dump inode->i_ino and super->s_dev. In
some cases, the dumped values differ from what is returned via stat(2)
or statx(2).
On Fri, May 18, 2018 at 03:04:13PM -0700, Darrick J. Wong wrote:
> On Fri, May 18, 2018 at 02:57:27PM -0700, Mark Fasheh wrote:
> > Right now we return EINVAL if a process does not have permission to dedupe a
> > file. This was an oversight on my part. EPERM gives a t
On Fri, May 18, 2018 at 03:03:38PM -0700, Darrick J. Wong wrote:
> > +/* Check whether we are allowed to dedupe the destination file */
> > +static int allow_file_dedupe(struct file *file)
>
> Shouldn't this return bool? It's a predicate, after all...
Yeah that should be bool. Thanks for
Hi,
The following patches fix a couple of issues with the permission
check we do in vfs_dedupe_file_range().
The first patch expands our check to allow dedupe of a file if the
user owns it or otherwise would be allowed to write to it.
Current behavior is that we'll allow dedupe only if:
- the
on the target if:
- the root or admin is asking for it
- the process has write access
- the owner of the file is asking for the dedupe
- the process could get write access
That way users can open read-only and still get dedupe.
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/read_write.
Right now we return EINVAL if a process does not have permission to dedupe a
file. This was an oversight on my part. EPERM gives a true description of
the nature of our error, and EINVAL is already used for the case that the
filesystem does not support dedupe.
Signed-off-by: Mark Fasheh <m
On Thu, May 17, 2018 at 01:15:51AM -0400, Zygo Blaxell wrote:
> On Sun, May 13, 2018 at 11:26:39AM -0700, Darrick J. Wong wrote:
> > On Sun, May 13, 2018 at 06:21:52PM +0000, Mark Fasheh wrote:
> > > On Fri, May 11, 2018 at 05:06:34PM -0700, Darrick J. Wong wrote:
> >
On Sun, May 13, 2018 at 10:50:25PM +0200, Adam Borowski wrote:
> On Sun, May 13, 2018 at 06:16:53PM +0000, Mark Fasheh wrote:
> > On Sat, May 12, 2018 at 04:49:20AM +0200, Adam Borowski wrote:
> > > On Fri, May 11, 2018 at 12:26:50PM -0700, Mark Fasheh wrote:
> >
On Fri, May 11, 2018 at 05:06:34PM -0700, Darrick J. Wong wrote:
> On Fri, May 11, 2018 at 12:26:51PM -0700, Mark Fasheh wrote:
> > Right now we return EINVAL if a process does not have permission to dedupe a
> > file. This was an oversight on my part. EPERM gives a t
Hey Adam,
On Sat, May 12, 2018 at 04:49:20AM +0200, Adam Borowski wrote:
> On Fri, May 11, 2018 at 12:26:50PM -0700, Mark Fasheh wrote:
> > The permission check in vfs_dedupe_file_range() is too coarse - We
> > only allow dedupe of the destination file if the user is root, o
Right now we return EINVAL if a process does not have permission to dedupe a
file. This was an oversight on my part. EPERM gives a true description of
the nature of our error, and EINVAL is already used for the case that the
filesystem does not support dedupe.
Signed-off-by: Mark Fasheh <m
- the process has write access
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/read_write.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/read_write.c b/fs/read_write.c
index c4eabbfc90df..77986a2e2a3b 100644
--- a/fs/read_write.c
+++ b/fs/read_write.c
@@ -2036,7 +
Hi,
The following patches fix a couple of issues with the permission
check we do in vfs_dedupe_file_range().
The first patch expands our check to allow dedupe of a readonly file
if the user owns it. Existing behavior is that we'll allow dedupe only
if:
- the user is an admin (root)
- the user
Hi,
The VFS's super_block covers a variety of filesystem functionality. In
particular we have a single structure representing both I/O and
namespace domains.
There are requirements to de-couple this functionality. For example,
filesystems with more than one root (such as btrfs subvolumes) can
, fs_view gets
an embedded super_block pointer. A helper function, inode_sb() is
introduced to make getting the superblock from an inode less clunky.
Filesystems need no functional changes, and the only additional memory
usage here is the added pointer on struct super_block.
Signed-off-by: Mark
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/aio.c | 6 ++--
fs/attr.c| 12 +++
fs/binfmt_misc.c | 6 ++--
fs/block_dev.c | 2 +-
fs/cachefiles/rdwr.c | 4 +--
fs/dcache.c | 8 ++---
fs/direct-io.c | 8 ++---
fs/event
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
arch/arc/kernel/troubleshoot.c| 2 +-
arch/powerpc/platforms/cell/spufs/inode.c | 6 +++---
arch/s390/hypfs/inode.c | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arc/
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
include/linux/backing-dev.h | 4 +-
include/linux/cleancache.h | 2 +-
include/linux/fs.h | 29 +-
include/linux/fscrypt_supp.h | 4 +-
include/linux/hugetlb.h | 2 +-
include/linux/nf
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
ipc/mqueue.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ipc/mqueue.c b/ipc/mqueue.c
index a808f29d4c5a..ac65b309c393 100644
--- a/ipc/mqueue.c
+++ b/ipc/mqueue.c
@@ -106,7 +106,7 @@ static inline
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
drivers/block/loop.c | 6 ++---
drivers/infiniband/hw/qib/qib_fs.c | 2 +-
drivers/md/md-bitmap.c | 2 +-
drivers/staging/lustre/lustre/llite/dir.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
security/apparmor/apparmorfs.c | 4 ++--
security/commoncap.c | 8
security/inode.c | 2 +-
security/integrity/evm/evm_crypto.c | 4 ++--
security/integrity/ima/ima_policy.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
kernel/audit.c | 2 +-
kernel/audit_fsnotify.c | 2 +-
kernel/audit_watch.c| 5 +++--
kernel/auditsc.c| 8
kernel/bpf/inode.c | 6 +++---
kernel/bpf/offload.c| 4 ++--
kernel/events/core.c| 4 ++--
7
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/9p/acl.c| 3 ++-
fs/9p/v9fs.h | 2 +-
fs/9p/vfs_inode.c | 8
fs/9p/vfs_inode_dotl.c | 14 +++---
4 files changed, 14 insertions(+), 13 deletions(-)
diff --git a/fs/9p/acl.c b/fs/9p/acl.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/adfs/dir.c | 6 +++---
fs/adfs/inode.c | 8
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/fs/adfs/dir.c b/fs/adfs/dir.c
index 29444c83da48..e28357fcb2d4 100644
--- a/fs/adfs/dir.c
+++ b/fs/adfs/dir.c
@@ -20,7
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/affs/amigaffs.c | 10 +-
fs/affs/bitmap.c | 2 +-
fs/affs/dir.c | 2 +-
fs/affs/file.c | 28 ++--
fs/affs/inode.c| 16
fs/affs/namei.c| 12 ++--
fs/affs/sym
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/afs/callback.c | 2 +-
fs/afs/dir.c | 8
fs/afs/file.c | 2 +-
fs/afs/write.c| 4 ++--
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/fs/afs/callback.c b/fs/afs/callback.c
index f4291b576054..73371c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
net/sunrpc/auth_gss/auth_gss.c | 4 ++--
net/sunrpc/rpc_pipe.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/net/sunrpc/auth_gss/auth_gss.c b/net/sunrpc/auth_gss/auth_gss.c
index 9463af4b32e8..3560956424fe
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
mm/cleancache.c | 10 +-
mm/filemap.c| 12 ++--
mm/hugetlb.c| 2 +-
mm/memory-failure.c | 2 +-
mm/shmem.c | 29 +++--
mm/swapfile.c | 4 ++--
6 files chang
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/autofs4/dev-ioctl.c | 2 +-
fs/autofs4/root.c | 20 ++--
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/fs/autofs4/dev-ioctl.c b/fs/autofs4/dev-ioctl.c
index b7c816f39404..6b28b01e5022 100644
--
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/befs/linuxvfs.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/fs/befs/linuxvfs.c b/fs/befs/linuxvfs.c
index af2832aaeec5..fc997025b9a0 100644
--- a/fs/befs/linuxvfs.c
+++ b/fs/befs/linuxvfs.c
@@ -131,7
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/ceph/addr.c | 2 +-
fs/ceph/caps.c | 16
fs/ceph/dir.c| 24
fs/ceph/file.c | 16
fs/ceph/inode.c | 16
fs/ceph/ioctl.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/btrfs/compression.c | 4 +-
fs/btrfs/ctree.h| 2 +-
fs/btrfs/delayed-inode.c| 4 +-
fs/btrfs/disk-io.c | 8 +--
fs/btrfs/export.c | 4 +-
fs/btrfs/extent-tree.c | 14 ++---
fs
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/cifs/cifsacl.c | 4 ++--
fs/cifs/cifsfs.c| 4 ++--
fs/cifs/cifsglob.h | 2 +-
fs/cifs/dir.c | 29 -
fs/cifs/file.c | 42 ++
fs/cifs/fscache.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/bfs/dir.c | 23 ---
fs/bfs/file.c | 4 ++--
fs/bfs/inode.c | 16 +---
3 files changed, 23 insertions(+), 20 deletions(-)
diff --git a/fs/bfs/dir.c b/fs/bfs/dir.c
index ee832ca5f734..124c1eedb53c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/coda/dir.c | 25 +
fs/coda/file.c| 7 ---
fs/coda/inode.c | 4 ++--
fs/coda/pioctl.c | 4 ++--
fs/coda/symlink.c | 2 +-
5 files changed, 22 insertions(+), 20 deletions(-)
diff --git a/fs/coda/d
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/configfs/inode.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/configfs/inode.c b/fs/configfs/inode.c
index ad718e5e37bb..4f28a7445336 100644
--- a/fs/configfs/inode.c
+++ b/fs/configfs/inode.c
@@ -91,13
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/crypto/bio.c | 10 +-
fs/crypto/crypto.c | 4 ++--
fs/crypto/fname.c | 4 ++--
fs/crypto/keyinfo.c | 8
fs/crypto/policy.c | 12 ++--
5 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/fs/
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/cramfs/inode.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index 017b0ab19bc4..eb633de7ccbe 100644
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
@@
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/ecryptfs/crypto.c | 5 ++---
fs/ecryptfs/file.c | 5 ++---
fs/ecryptfs/inode.c | 15 +++
3 files changed, 11 insertions(+), 14 deletions(-)
diff --git a/fs/ecryptfs/crypto.c b/fs/ecryptfs/crypto.c
index 846ca1
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/exportfs/expfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/exportfs/expfs.c b/fs/exportfs/expfs.c
index 329a5d103846..d0ce48374bda 100644
--- a/fs/exportfs/expfs.c
+++ b/fs/exportfs/expfs.c
@@ -383,7 +383,7 @@
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/efivarfs/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/efivarfs/inode.c b/fs/efivarfs/inode.c
index 71ff317e..5e0de72476bf 100644
--- a/fs/efivarfs/inode.c
+++ b/fs/efivarfs/inode.c
@@ -92,7 +92,7 @@
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/ext2/balloc.c | 10 +++
fs/ext2/dir.c| 32 ++--
fs/ext2/file.c | 6 ++--
fs/ext2/ialloc.c | 16 +-
fs/ext2/inode.c | 82 +++-
fs/ext2/i
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/f2fs/data.c | 6 +++---
fs/f2fs/f2fs.h | 2 +-
fs/f2fs/file.c | 36 ++--
fs/f2fs/inline.c | 4 ++--
fs/f2fs/inode.c| 6 +++---
fs/f2fs/namei.c| 11 ++-
fs/f2fs/recovery.
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/exofs/dir.c | 6 +++---
fs/exofs/inode.c | 12 ++--
fs/exofs/namei.c | 4 ++--
3 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/fs/exofs/dir.c b/fs/exofs/dir.c
index f0138674c1ed..592471362243 100644
--- a/fs
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/efs/dir.c | 2 +-
fs/efs/file.c| 2 +-
fs/efs/inode.c | 6 +++---
fs/efs/namei.c | 4 ++--
fs/efs/symlink.c | 4 ++--
5 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/fs/efs/dir.c b/fs/efs/dir.c
index f892ac
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/fat/cache.c | 12 ++--
fs/fat/dir.c | 26 +-
fs/fat/fat.h | 2 +-
fs/fat/fatent.c | 10 +-
fs/fat/file.c| 24
fs/fat/inode.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/fuse/dir.c| 13 +++--
fs/fuse/file.c | 6 +++---
fs/fuse/fuse_i.h | 2 +-
fs/fuse/inode.c | 7 ---
4 files changed, 15 insertions(+), 13 deletions(-)
diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
index 249673
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/freevxfs/vxfs_bmap.c | 14 +++---
fs/freevxfs/vxfs_inode.c | 2 +-
fs/freevxfs/vxfs_lookup.c | 10 +-
fs/freevxfs/vxfs_subr.c | 4 ++--
4 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/fs/fr
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/hfs/attr.c| 4 ++--
fs/hfs/catalog.c | 10 +-
fs/hfs/dir.c | 11 ++-
fs/hfs/extent.c | 10 +-
fs/hfs/inode.c | 32
5 files changed, 34 insertions(+), 33 deletions(-)
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/gfs2/aops.c| 9 +
fs/gfs2/bmap.c| 9 +
fs/gfs2/dir.c | 3 ++-
fs/gfs2/export.c | 2 +-
fs/gfs2/file.c| 4 ++--
fs/gfs2/incore.h | 2 +-
fs/gfs2/inode.c | 8
fs/gfs2/meta_io.h | 2 +-
fs/gfs2/s
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/hfsplus/attributes.c | 12 ++--
fs/hfsplus/bnode.c | 2 +-
fs/hfsplus/catalog.c| 12 ++--
fs/hfsplus/dir.c| 22 +++---
fs/hfsplus/extents.c| 11 ++-
fs/hfsplus/inode.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/hpfs/dir.c | 76 +---
fs/hpfs/dnode.c | 176
fs/hpfs/ea.c| 2 +-
fs/hpfs/file.c | 45 ---
fs/hpfs/inode.c | 77 +--
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/hostfs/hostfs_kern.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/hostfs/hostfs_kern.c b/fs/hostfs/hostfs_kern.c
index c148e7f4f451..b99d08b7ef34 100644
--- a/fs/hostfs/hostfs_kern.c
+++ b/fs/hostfs/hostfs_
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/jffs2/dir.c | 16
fs/jffs2/file.c | 8
fs/jffs2/fs.c| 8
fs/jffs2/xattr.c | 6 +++---
4 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/fs/jffs2/dir.c b/fs/jffs2/dir.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/hugetlbfs/inode.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
index b9a254dcc0e7..31d2a6051bea 100644
--- a/fs/hugetlbfs/inode.c
+++ b/fs/hugetlbfs/inode.c
@@
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/jbd2/journal.c | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
index 3fbf48ec2188..e1834a69cd41 100644
--- a/fs/jbd2/journal.c
+++ b/fs/jbd2/journal.c
@@ -1
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/isofs/dir.c| 2 +-
fs/isofs/export.c | 6 +++---
fs/isofs/inode.c | 22 --
fs/isofs/joliet.c | 4 ++--
fs/isofs/namei.c | 4 ++--
fs/isofs/rock.c | 29 +++--
6 files changed, 35 inse
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/jfs/acl.c | 2 +-
fs/jfs/file.c | 6 +--
fs/jfs/inode.c| 14 +++
fs/jfs/ioctl.c| 2 +-
fs/jfs/jfs_discard.c | 12 +++---
fs/jfs/jfs_dmap.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/minix/bitmap.c | 18 ++
fs/minix/dir.c | 18 +-
fs/minix/inode.c| 10 +-
fs/minix/itree_common.c | 10 +-
fs/minix/itree_v1.c | 6 +++---
fs/minix/itree_v2.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/lockd/svclock.c | 8
fs/lockd/svcsubs.c | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/fs/lockd/svclock.c b/fs/lockd/svclock.c
index 3701bccab478..d13892c7bd89 100644
--- a/fs/lockd/svclock.c
+++ b/fs
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/nfsd/blocklayout.c | 4 ++--
fs/nfsd/export.c | 8
fs/nfsd/nfs4recover.c | 2 +-
fs/nfsd/nfsctl.c | 4 ++--
fs/nfsd/nfssvc.c | 5 +++--
fs/nfsd/vfs.c | 8
6 files changed, 16 insertions(+), 15 del
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/kernfs/dir.c | 4 ++--
fs/kernfs/inode.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/kernfs/dir.c b/fs/kernfs/dir.c
index 89d1dc19340b..1239244e826a 100644
--- a/fs/kernfs/dir.c
+++ b/fs/kernfs/dir.c
@@ -
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/nilfs2/alloc.c | 10 -
fs/nilfs2/bmap.c| 4 ++--
fs/nilfs2/btnode.c | 6 +++---
fs/nilfs2/btree.c | 12 +--
fs/nilfs2/cpfile.c | 6 +++---
fs/nilfs2/dat.c | 2 +-
fs/nilfs2/dir.c
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/nfs/blocklayout/rpc_pipefs.c| 2 +-
fs/nfs/callback_proc.c | 4 ++--
fs/nfs/dir.c | 22 +-
fs/nfs/export.c| 2 +-
fs/nfs/
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/ntfs/aops.c| 16 ++--
fs/ntfs/bitmap.c | 11 ++-
fs/ntfs/dir.c | 10 ++-
fs/ntfs/file.c| 30 ---
fs/ntfs/inode.c | 231 +-
fs/ntfs/inode.h | 2 +-
fs/ntfs/log
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/notify/fdinfo.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/notify/fdinfo.c b/fs/notify/fdinfo.c
index d478629c728b..857df5ce27ac 100644
--- a/fs/notify/fdinfo.c
+++ b/fs/notify/fdinfo.c
@@ -91,7 +91,8 @@
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/overlayfs/export.c | 2 +-
fs/overlayfs/inode.c | 6 +++---
fs/overlayfs/super.c | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/overlayfs/export.c b/fs/overlayfs/export.c
index 87bd4148f4fb..41b23510f5b9
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/omfs/dir.c | 24
fs/omfs/file.c | 37 +++--
fs/omfs/inode.c | 19 ++-
3 files changed, 41 insertions(+), 39 deletions(-)
diff --git a/fs/omfs/dir.c b/fs/omfs
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/openpromfs/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/openpromfs/inode.c b/fs/openpromfs/inode.c
index 2200662a9bf1..d1c59e6252c5 100644
--- a/fs/openpromfs/inode.c
+++ b/fs/openpromfs/inode.c
@@ -229,7
1 - 100 of 477 matches
Mail list logo
