similar to: [PATCH] xfstests: add 'check -btrfs' support

Btrfs had some issues with fsync()''ing directories and fsync()''ing after renames. These three new tests cover the 3 different issues we were seeing. This breaks out the dmflakey stuff into a common helper to be shared between generic/311 and generic/320. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- V1->V2: moved this out into its own test instead of

I''ve noticed that fstyp on a floppy media formatted with "pcfs" now needs somewhere between 30 - 100 seconds to find out that the floppy media is formatted with "pcfs". E.g. on sparc snv_48, I currently observe this: % time fstyp /vol/dev/rdiskette0/nomedia pcfs 0.01u 0.10s 1:38.84 0.1% zfs''s /usr/lib/fs/zfs/fstyp.so.1 seems to add about 40 seconds to that

Btrfs had some issues with fsync()''ing directories and fsync()''ing after renames. These three new tests cover the 3 different issues we were seeing. This breaks out the dmflakey stuff into a common helper to be shared between generic/311 and generic/321. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- V1->V2: rename test to generic/321 -removed an

The patch is against 3.1-rc3. struct vring_used has two __u16 fields plus array of struct vring_used_elem. Current vring_size counts the __u16 fields to 3. Fix it to 2 in the patch. Signed-off-by: Wang Sheng-Hui <shhuiw at gmail.com> --- include/linux/virtio_ring.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/linux/virtio_ring.h

The patch is against 3.1-rc3. struct vring_used has two __u16 fields plus array of struct vring_used_elem. Current vring_size counts the __u16 fields to 3. Fix it to 2 in the patch. Signed-off-by: Wang Sheng-Hui <shhuiw at gmail.com> --- include/linux/virtio_ring.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/linux/virtio_ring.h

The memory allocation failure is BUG_ON in add_excluded_extent (following the code path). No need to BUG_ON -ENOMEM inside btrfs_alloc_logged_file_extent. Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com> --- fs/btrfs/extent-tree.c | 6 ++---- 1 files changed, 2 insertions(+), 4 deletions(-) diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c index 95492cc..9b9a6fa 100644 ---

From: Joerg Roedel <jroedel at suse.de> All drivers are converted to use the probe/release_device() call-backs, so the add_device/remove_device() pointers are unused and the code using them can be removed. Signed-off-by: Joerg Roedel <jroedel at suse.de> --- drivers/iommu/iommu.c | 149 ++++++++---------------------------------- include/linux/iommu.h | 4 -- 2 files changed, 29

the following is the code of the controller, under the dir components/test/: class Test::GroupsManController < ApplicationController uses_component_template_root def add_to_group @account = Account.find_by_nick(@params[:nick]) # render :text => "#{session[:account_id]} #{Group.find(session[:group_id]).owner_id}" if (session[:account_id] ==

From: Joerg Roedel <jroedel at suse.de> When a bus is initialized with iommu-ops, all devices on the bus are scanned and iommu-groups are allocated for them, and each groups will also get a default domain allocated. Until now this happened as soon as the group was created and the first device added to it. When other devices with different default domain requirements were added to the group

I''ve cloned: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git When I build I get compile errors trying to build dmapi. Do I need to build this? I''ve attached a log of the build (build.log). If I ignore the build error and just go ahead and try to run the tests my first question is, "What do I run?". Looking at the README it looks like I want to run

This is similar to a previous fix I sent. 1 gig makes us do mixed file block groups for btrfs, so these enospc tests will usually fail because we don''t have space for metadata, which is the case for this test. So jack the size up to 1.5gig so that btrfs can do its normal thing and pass the test. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- tests/generic/256 |

Not sure how this happened, but filter.btrfs including itself leads to immense sadness for any file that includes it. (I got a segfault when I tried to run 307) Signed-off-by: Eric Sandeen <sandeen@redhat.com> --- diff --git a/common/filter.btrfs b/common/filter.btrfs index b1aa733..99d04a6 100644 --- a/common/filter.btrfs +++ b/common/filter.btrfs @@ -1,7 +1,5 @@ # Filters for btrfs

mkfs supports the option -V/--version. Add its description to print_usage(). Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com> --- mkfs.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/mkfs.c b/mkfs.c index 47f0c9c..2cc6051 100644 --- a/mkfs.c +++ b/mkfs.c @@ -349,6 +349,7 @@ static void print_usage(void) fprintf(stderr, "\t -s --sectorsize min block

I''m running into a problem with the btrfs-cleaner thread becoming blocked on xfstests 068. The test locks up indefinitely without completing (normally it finished in about 45 seconds on my test box). I''ve replicated the issue on 3.10.0_rc5 and the for-linus branch of 3.9.0. I ran a git bisect on the 3.9.0 for-linus branch, and tracked my issue to the following commit: commit

Three kind of structures need to be freed on close: * All struct btrfs_device managed by fs_devices * The name field for each struct btrfs_device * The above items for seed_devices Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com> --- volumes.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/volumes.c b/volumes.c index

I''m not sure how the numbering is supposed to work now that we''ve split everything out so I''m just going with the next number in the directory. This is a regression test for btrfs send, we had a problem where we''d try to send a file that had been deleted in the source snapshot. This is just to make sure we don''t have the same problem in the future.

From: Joerg Roedel <jroedel at suse.de> This is needed to defer default_domain allocation for new IOMMU groups until all devices have been added to the group. Signed-off-by: Joerg Roedel <jroedel at suse.de> --- drivers/iommu/iommu.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c index

Hi list, I have write down my code on which chanspy not working when I make a group with name of spy. Please help me where is the issue on that. a) caller will call this number to join konference and spy group exten => 43681111,1,Answer() exten => 43681111,n,NoOp(****${CHANNEL}****) exten => 43681111,n,Set(GROUP(${CHANNEL})=spy) exten => 43681111,n,Set(a=${GROUP_LIST(spy)}) exten

So if you have a mount command that doesn''t use /etc/mtab then it will spit out a different device for the mounted device. So say we have SCRATCH_DEV_POOL="/dev/sda /dev/sdb /dev/sdc" we will turn this into SCRATCH_DEV="/dev/sda" SCRATCH_DEV_POOL="/dev/sdb /dev/sdc" and then when you mkfs this you do _scratch_mkfs $SCRATCH_DEV_POOL which turns into this

I have a macro and when I call it I have something like this: exten => s,1,NoOp(Group Count: ${GROUP_COUNT(MYGROUP)}) exten => s,n,Set(GROUP()=MYGROUP) ;Set Group exten => s,n,NoOp(Group List: ${GROUP_LIST()}) exten => s,n,NoOp(Group Count: ${GROUP_COUNT(MYGROUP)}) The GROUP_COUNT returns zero before the call to GROUP but also returns 0 after the call to GROUP. If I