search for: byte_offset

...=0A = if (m{^block (\d+): \S+ \d+/\d+\s+(\d+)\s.*/0*(\d+)$}) {=0A = my $offset =3D $1; # block offset in tar file=0A my $size = =3D $2; # size in bytes in tar file=0A my $filename =3D $3;= # filename in tar file, without leading 0s=0A my $byte_offset = =3D (1 + $offset) * 512; # byte offset in tar file=0A $block{$fi= lename} =3D { size =3D> $size, offset =3D> $byte_offset };=0A #p= rintf ("%s %d %d\n", $filename, $byte_offset, $size);=0A=0A if (= $byte_offset + $size > $estimated_size) {=0A...

In dispatch_rw_block_io after a call to HYPERVISOR_grant_table_op, there is the following code which calls fast_flush_area and breaks out of the loop early if one of the handles returned from HYPERVISOR_grant_table_op is negative: for (i = 0; i < nseg; i++) { if (unlikely(map[i].handle < 0)) { DPRINTK("invalid buffer -- could not remap it\n"); fast_flush_area(pending_idx,

Add a couple of documentation details about PV-GRUB support - the menu.lst content can be passed as a ramdisk. - virtual partitions are not supported. Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> diff -r b8d2a4134a68 stubdom/README --- a/stubdom/README Wed Mar 03 17:41:58 2010 +0000 +++ b/stubdom/README Wed Mar 03 20:42:53 2010 +0100 @@ -52,11 +52,17 @@ extra =

Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Hank Janssen <hjanssen at microsoft.com> --- drivers/staging/hv/channel.c | 48 ++++++------ drivers/staging/hv/channel_mgmt.c | 48 ++++++------ drivers/staging/hv/connection.c | 154 ++++++++++++++++++------------------ drivers/staging/hv/vmbus_drv.c | 2 +-

Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Hank Janssen <hjanssen at microsoft.com> --- drivers/staging/hv/channel.c | 48 ++++++------ drivers/staging/hv/channel_mgmt.c | 48 ++++++------ drivers/staging/hv/connection.c | 154 ++++++++++++++++++------------------ drivers/staging/hv/vmbus_drv.c | 2 +-

...+ * > + * Iterate in reverse over the sequence numbers. If the filename is: > + * > + * "ABCDEFGHIJKLMNO" > + * > + * assuming those are UCS-2 codepoints, so lfn_size = 15*2 = 30, > + * then we generate these LFN sequences: > + * > + * seq byte_offset s[13] > + * 0x42 26 "NO " > + * 0x01 0 "ABCDEFGHIJKLM" > + */ > + for (seq = 1 + lfn->lfn_size/2/13; seq >= 1; --seq) { > + size_t byte_offset = (seq-1)*2*13, r; And again > + uint16_t s[13]; > +...

Hi all, This patch set adds batched discard support to ocfs2. Please check. Thanks. Regards, Tao

2017-11-15 21:29 GMT+01:00 Richard W.M. Jones <rjones@redhat.com>: > Gandalf, is there an XVA file publically available (pref. not > too big) that we can look at? I can try to provide one, but it's simple: # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 ---------- 0/0 42353 1970-01-01 01:00 ova.xml ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000

boy, if you really care about your problem, *USE* ext3-users: > oh, and please respond on-list, perhaps other ppl are curious > about some details too ;) really. Tobias Amon schrieb: > Hi, > > I use e2fsprogs version 1.5.2 (I think) http://e2fsprogs.sourceforge.net/ exists, latest version is 1.35. > I got another solution. Yast, which came with Suse > is not able to

Add nbdkit-floppy-plugin, “inspired” by qemu's VVFAT driver, but without the ability to handle writes. The implementation is pretty complete, supporting FAT32, LFNs, volume labels, timestamps, etc, and it passes both ‘make check’ and ‘make check-valgrind’. Usage is simple; to serve the current directory: $ nbdkit floppy . Then using guestfish (or any NBD client): $ guestfish --ro

...***************************************************************************/ -static void base64_encode(char *buf, int len, char *out) +void base64_encode(char *buf, int len, char *out) { char *b64 = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/"; int bit_offset, byte_offset, idx, i; diff -u rsync-2.5.6.orig/socket.c rsync-2.5.6/socket.c --- rsync-2.5.6.orig/socket.c Mon Jan 27 04:35:09 2003 +++ rsync-2.5.6/socket.c Tue May 13 13:18:55 2003 @@ -33,17 +33,56 @@ #include "rsync.h" +/** + *declare the base64_encode function from authenticate.c + **/ +void b...

...***************************************************************************/ -static void base64_encode(char *buf, int len, char *out) +void base64_encode(char *buf, int len, char *out) { char *b64 = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/"; int bit_offset, byte_offset, idx, i; diff -u rsync-2.5.5.orig/socket.c rsync-2.5.5/socket.c --- rsync-2.5.5.orig/socket.c 2002-03-16 10:00:44.000000000 +0100 +++ rsync-2.5.5/socket.c 2002-04-04 12:32:58.000000000 +0200 @@ -33,15 +33,52 @@ #include "rsync.h" +/* declare the base64_encode function from authentica...

...n->short_ext[j]; + + /* LFN support. + * + * Iterate in reverse over the sequence numbers. If the filename is: + * + * "ABCDEFGHIJKLMNO" + * + * assuming those are UCS-2 codepoints, so lfn_size = 15*2 = 30, + * then we generate these LFN sequences: + * + * seq byte_offset s[13] + * 0x42 26 "NO " + * 0x01 0 "ABCDEFGHIJKLM" + */ + for (seq = 1 + lfn->lfn_size/2/13; seq >= 1; --seq) { + size_t byte_offset = (seq-1)*2*13, r; + uint16_t s[13]; + + /* Copy the portion of the LFN into s. +...

Hi, The following patches add support for ext4 and btrfs to PV-GRUB. These patches are taken nearly verbatim from those provided by Fedora and Gentoo. We''ve been using these patches for the PV-GRUB images available in EC2 for some time now with no problems. Changes from v1: - Makefile has been changed to check the exit code from patch - The btrfs patch has been rebased to apply

Hi all, Somehow I managed to mess with a RAID array containing an ext3 partition. Parenthesis, if it matters: I disconnected physically a drive while the array was online. Next thing, I lost the right order of the drives in the array. While trying to re-create it, I overwrote the raid superblocks. Luckily, the array was RAID5 degraded, so whenever I re-created it, it didn't go into sync;

This patch set removes all un-needed DPRINT and printk calls and replaces the remaining ones with the correct pr_, dev_ and netdev_ calls from hv_vmbus, hv_netvsc, hv_timesource and hv_utils. Several DPRINTS are remaining that will be cleaned up in my next set of patches. They deal with printing out certain debugging that will be implemented slightly differently. The remaining hv_storvsc and

This patch set removes all un-needed DPRINT and printk calls and replaces the remaining ones with the correct pr_, dev_ and netdev_ calls from hv_vmbus, hv_netvsc, hv_timesource and hv_utils. Several DPRINTS are remaining that will be cleaned up in my next set of patches. They deal with printing out certain debugging that will be implemented slightly differently. The remaining hv_storvsc and

Further cleanup of the hv drivers. 1) Implement code for autoloading the vmbus drivers without using PCI or DMI signatures. I have implemented this based on Greg's feedback on my earlier implementation. 2) Cleanup error handling across the board and use standard Linux error codes. 3) General cleanup Regards, K. Y

Further cleanup of the hv drivers. 1) Implement code for autoloading the vmbus drivers without using PCI or DMI signatures. I have implemented this based on Greg's feedback on my earlier implementation. 2) Cleanup error handling across the board and use standard Linux error codes. 3) General cleanup Regards, K. Y

Further cleanup of the hv drivers. Back in June I had sent two patch sets to address these issues. I have addressed the comments I got from the community on my earlier patches here: 1) Implement code for autoloading the vmbus drivers without using PCI or DMI signatures. I have implemented this based on Greg's feedback on my earlier implementation. 2) Cleanup error handling across