- Original Message -
On Tue, Apr 14, 2015 at 10:47 AM, Bob Peterson rpete...@redhat.com wrote:
12 files changed, 184 insertions(+), 95 deletions(-)
Oh, and this was incorrect. You had apparently limited the statistics
to the fs/gfs2 directory, and thus missed the changes to the
Hi,
Linus has pulled the latest set of patches from the for-next branch of
the linux-gfs2.git tree, so I rebased the tree based on Linus's master.
So the current tree is back to having no unmerged GFS2 patches.
Regards,
Bob Peterson
Red Hat File Systems
This patch reverses the recent set of i_goal fixes for fsck.gfs2.
This is because of two problems.
1. It is not possible to determine if a valid block within the fs
is the correct goal block for a given inode.
2. Conversely, given an inode, it is also not possible to accurately
determine what its
Hi,
This patch changes function gfs2_rgrp_congested so that it uses an
average srttb (smoothed round trip time for blocking rgrp glocks)
rather than the CPU-specific value. If we use the CPU-specific value
it can incorrectly report no contention when there really is contention
due to the glock
Hi,
On 15/04/15 15:39, Bob Peterson wrote:
Hi,
This patch changes function gfs2_rgrp_congested so that it uses an
average srttb (smoothed round trip time for blocking rgrp glocks)
rather than the CPU-specific value. If we use the CPU-specific value
it can incorrectly report no contention when
Hi Abhi,
On 15/04/15 14:37, Abhi Das wrote:
This patch reverses the recent set of i_goal fixes for fsck.gfs2.
This is because of two problems.
1. It is not possible to determine if a valid block within the fs
is the correct goal block for a given inode.
2. Conversely, given an inode, it is also
Hi,
- Original Message -
At the end of gfs2_set_inode_flags inode-i_flags is set to flags, so
we should be mondifying flags instead of inode-i_flags, so it isn't
Patch looks good, but mondifying looks like a type and should probably be
fixed.
Regards,
Bob Peterson
Red Hat File
Hi,
Looks good to me except for a few nits:
(snip)
Just a suggestion, but can you add a function comment at the start of this
function?
+static int gfs2_exchange(struct inode *odir, struct dentry *odentry,
+ struct inode *ndir, struct dentry *ndentry,
+
At the end of gfs2_set_inode_flags inode-i_flags is set to flags, so
we should be mondifying flags instead of inode-i_flags, so it isn't
overwritten.
Signed-off-by: Benjamin Marzinski bmarz...@redhat.com
---
fs/gfs2/file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
gfs2 now uses the rename2 directory iop, and supports the
RENAME_EXCHANGE flag (as well as RENAME_NOREPLACE, which the vfs
takes care of).
Signed-off-by: Benjamin Marzinski bmarz...@redhat.com
---
fs/gfs2/inode.c | 192 +++-
1 file changed, 177
At the end of gfs2_set_inode_flags inode-i_flags is set to flags, so
we should be modifying flags instead of inode-i_flags, so it isn't
overwritten.
Signed-off-by: Benjamin Marzinski bmarz...@redhat.com
---
fs/gfs2/file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
gfs2 now uses the rename2 directory iop, and supports the
RENAME_EXCHANGE flag (as well as RENAME_NOREPLACE, which the vfs
takes care of).
Signed-off-by: Benjamin Marzinski bmarz...@redhat.com
---
fs/gfs2/inode.c | 205 +++-
1 file changed, 189
Hi,
On 15/04/15 00:16, Linus Torvalds wrote:
On Tue, Apr 14, 2015 at 10:47 AM, Bob Peterson rpete...@redhat.com wrote:
There's another that adds me as a GFS2 co-maintainer [...]
So generally, when I start getting pull requests from different
people, I'd like to see a previous separate
13 matches
Mail list logo
