search for: dest_offset

On Thu, 27 Oct 2016 15:39:27 -0700, Jeremy Allison <jra at samba.org> wrote : > On Fri, Oct 28, 2016 at 12:08:50AM +0200, Saint Germain via samba > wrote: > > On Thu, 27 Oct 2016 14:50:48 -0700, Jeremy Allison <jra at samba.org> > > wrote : > > > > > > Server-side copy can be requested using smbclient, using > > > the "scopy"

...=0x8f7e0) at mbox-sync-update.c:267 No locals. #5 0x00041730 in mbox_sync_rewrite (sync_ctx=0xffbff548, mail_ctx=0x39d5, end_offset=14098141, move_diff=27645, extra_space=1, first_seq=45, last_seq=163) at mbox-sync-rewrite.c:552 mails = (struct mbox_sync_mail *) 0xcf238 offset = 1 dest_offset = 4294967295 next_end_offset = 14079696 next_move_diff = 6 start_offset = 1275633 expunged_space = 0 idx = 185 first_nonexpunged_idx = 0 padding_per_mail = 50 count = 542 ret = 0 __PRETTY_FUNCTION__ = "mktime(today) fail" #6 0x0003db84 in mbox_sync (mbox=0xc09c0, flags=32407386...

...BTRFS_FILE_EXTENT_REG || found_type == BTRFS_FILE_EXTENT_PREALLOC) { @@ -599,7 +600,8 @@ static noinline int replay_one_extent(struct btrfs_trans_handle *trans, ret = btrfs_insert_empty_item(trans, root, path, key, sizeof(*item)); - BUG_ON(ret); + if (ret) + goto out; dest_offset = btrfs_item_ptr_offset(path->nodes[0], path->slots[0]); copy_extent_buffer(path->nodes[0], eb, dest_offset, @@ -653,26 +655,30 @@ static noinline int replay_one_extent(struct btrfs_trans_handle *trans, ret = btrfs_lookup_csums_range(root->log_root, csum_start,...

...from saveload.c:269: /usr/include/sys/tihdr.h:241: parse error before `t_scalar_t' /usr/include/sys/tihdr.h:241: warning: no semicolon at end of struct or union /usr/include/sys/tihdr.h:242: warning: data definition has no type or storage class /usr/include/sys/tihdr.h:243: parse error before `DEST_offset' /usr/include/sys/tihdr.h:243: warning: data definition has no type or storage class /usr/include/sys/tihdr.h:244: parse error before `OPT_length' /usr/include/sys/tihdr.h:244: warning: data definition has no type or storage class /usr/include/sys/tihdr.h:245: parse error before `OPT_offs...

...or(errno), (unsigned long long)cr_args.src_length, (long long)cr_args.src_fd, (unsigned long long)cr_args.src_offset, dest_fsp->fh->fd, (unsigned long long)cr_args.dest_offset)); if you see any of these then it happened.

...span more than one ordered extent (+89/-4) Btrfs: avoid NULL pointer deref in try_release_extent_buffer (+4/-2) Btrfs: don''t use migrate page without CONFIG_MIGRATION (+6/-1) Btrfs: add migrate page for metadata inode (+25/-2) Li Zefan (3) commits (+6/-6): btrfs: Check if dest_offset is block-size aligned before cloning file (+3/-4) btrfs: Show device attr correctly for symlinks (+1/-0) btrfs: Set file size correctly in file clone (+2/-2) Miao Xie (3) commits (+195/-45): btrfs: cleanup duplicate bio allocating functions (+8/-18) btrfs: fix free dip and dip->...

...efore `t_scalar_t' Yoko> /usr/include/sys/tihdr.h:468: warning: no semicolon at end of Yoko> struct or union Yoko> /usr/include/sys/tihdr.h:469: warning: data definition has no type Yoko> or storage class Yoko> /usr/include/sys/tihdr.h:470: parse error before `DEST_offset' Yoko> /usr/include/sys/tihdr.h:470: warning: data definition has no type Yoko> or storage class Yoko> /usr/include/sys/tihdr.h:471: parse error before `OPT_length' Yoko> ***** Yoko> Is this version support Solaris7. -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-....

...(unsigned long long)cr_args.src_length, > (long long)cr_args.src_fd, > (unsigned long long)cr_args.src_offset, > dest_fsp->fh->fd, > (unsigned long long)cr_args.dest_offset)); > > if you see any of these then it happened. Ok I understand how to check that it happened, but how can I make sure that it doesn't happen ? How can I ensure that clone range request sizes are integer divisible by 4096 on my server ? Should I change something on the BTRFS filesystem...

I am trying to code a Web Service in rails that can handle file uploads. Now as i read, SOAP 1.1 doesn''t support this yet..so i will have to use SOAP4R, right? This is fine from server side...but will this API will be compatible to .NET clients, which will be using standard SOAP API perhaps. Any idea, whats the way to go here?

This patchset adds support for virtual IOMMU to the VMCI module. We switch to DMA consistent mappings for queuepair and doorbell pages that are passed to the device, which allows the module to work in the presence of vIOMMU/VT-d. Andy King (2): VMCI: Remove non-blocking/pinned queuepair support VMCI: Add support for virtual IOMMU drivers/misc/vmw_vmci/vmci_driver.c | 2 +-

This patchset adds support for virtual IOMMU to the VMCI module. We switch to DMA consistent mappings for queuepair and doorbell pages that are passed to the device, which allows the module to work in the presence of vIOMMU/VT-d. Andy King (2): VMCI: Remove non-blocking/pinned queuepair support VMCI: Add support for virtual IOMMU drivers/misc/vmw_vmci/vmci_driver.c | 2 +-

This patchset adds support for virtual IOMMU to the VMCI module. We switch to DMA consistent mappings for queuepair and doorbell pages that are passed to the device, which allows the module to work in the presence of vIOMMU/VT-d. Andy King (2): VMCI: Remove non-blocking/pinned queuepair support VMCI: Add support for virtual IOMMU drivers/misc/vmw_vmci/vmci_driver.c | 2 +-

This patchset adds support for virtual IOMMU to the VMCI module. We switch to DMA consistent mappings for queuepair and doorbell pages that are passed to the device, which allows the module to work in the presence of vIOMMU/VT-d. Andy King (2): VMCI: Remove non-blocking/pinned queuepair support VMCI: Add support for virtual IOMMU drivers/misc/vmw_vmci/vmci_driver.c | 2 +-

...diff --git a/drivers/misc/vmw_vmci/vmci_queue_pair.c b/drivers/misc/vmw_vmci/vmci_queue_pair.c index 8ff2e5e..8698e0c 100644 --- a/drivers/misc/vmw_vmci/vmci_queue_pair.c +++ b/drivers/misc/vmw_vmci/vmci_queue_pair.c @@ -148,12 +148,10 @@ typedef int vmci_memcpy_from_queue_func(void *dest, size_t dest_offset, struct vmci_queue_kern_if { struct page **page; struct page **header_page; - void *va; struct mutex __mutex; /* Protects the queue. */ struct mutex *mutex; /* Shared by producer and consumer queues. */ bool host; size_t num_pages; - bool mapped; }; /* @@ -267,11 +265,6 @@ static v...

...nclude <linux/module.h> #include <linux/mutex.h> #include <linux/pagemap.h> +#include <linux/pci.h> #include <linux/sched.h> #include <linux/slab.h> #include <linux/uio.h> @@ -146,12 +147,20 @@ typedef int vmci_memcpy_from_queue_func(void *dest, size_t dest_offset, /* The Kernel specific component of the struct vmci_queue structure. */ struct vmci_queue_kern_if { - struct page **page; - struct page **header_page; struct mutex __mutex; /* Protects the queue. */ struct mutex *mutex; /* Shared by producer and consumer queues. */ - bool host; - size_t nu...

...FS_FILE_EXTENT_REG || found_type == BTRFS_FILE_EXTENT_PREALLOC) { @@ -558,7 +558,7 @@ static noinline int replay_one_extent(struct btrfs_trans_handle *trans, ret = btrfs_insert_empty_item(trans, root, path, key, sizeof(*item)); - BUG_ON(ret); + btrfs_fixable_bug_on(ret); dest_offset = btrfs_item_ptr_offset(path->nodes[0], path->slots[0]); copy_extent_buffer(path->nodes[0], eb, dest_offset, @@ -592,7 +592,7 @@ static noinline int replay_one_extent(struct btrfs_trans_handle *trans, ret = btrfs_alloc_logged_file_extent(trans, root, root->root...

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later