search for: chksum

...} -static int gpt_check_hdr_crc(const struct disk_info * const diskinfo, struct disk_gpt_header **_gh) +static int valid_crc_hdr(void *buf) { - struct disk_gpt_header *gh = *_gh; - uint64_t lba_alt; - uint32_t hold_crc32; + struct disk_gpt_header *gh = buf; + uint32_t crc = gh->chksum; + int valid; - hold_crc32 = gh->chksum; gh->chksum = 0; - if (!valid_crc(hold_crc32, (const uint8_t *)gh, gh->hdr_size)) { - warn("Primary GPT header checksum invalid."); - /* retry with backup */ - lba_alt = gh->lba_alt; - free(gh); - if (!(gh = *_gh = disk_r...

...gid); - oct_it((long) size, 13, hb.dbuf.size); - oct_it((long) mtime, 13, hb.dbuf.mtime); + oct_it((SMB_BIG_UINT)0, 8, hb.dbuf.uid); + oct_it((SMB_BIG_UINT)0, 8, hb.dbuf.gid); + oct_it((SMB_BIG_UINT) size, 13, hb.dbuf.size); + oct_it((SMB_BIG_UINT) mtime, 13, hb.dbuf.mtime); memcpy(hb.dbuf.chksum, " ", sizeof(hb.dbuf.chksum)); memset(hb.dbuf.linkname, 0, NAMSIZ); hb.dbuf.linkflag=ftype; @@ -217,7 +217,7 @@ for (chk=0, i=sizeof(hb.dummy), jp=hb.dummy; --i>=0;) chk+=(0xFF & *jp++); - oct_it((long) chk, 8, hb.dbuf.chksum); + oct_it((SMB_BIG_UINT) chk, 8...

...erved +.res2 db 0 ; Reserved +.bustype equ ''PCI '' ; Host bus type (4 bytes, space padded) +.inttype equ ''ATA '' ; Interface type (8 bytes, spc. padded) +.intpath dd 0, 0 ; Interface path +.devpath dd 0, 0, 0, 0 ; Device path +.res3 db 0 ; Reserved +.chksum db 0 ; DPI checksum (not implemented) =20 %endif =20 diff --git a/memdisk/setup.c b/memdisk/setup.c index 98c4b69..b8efd8a 100644 --- a/memdisk/setup.c +++ b/memdisk/setup.c @@ -80,6 +80,16 @@ struct edd_dpt { uint64_t sectors; /* Total sectors */ uint16_t bytespersec; /* Bytes/secto...

...ffload is on, and then not duplicating the verification in Mirage would > have been an optimisation. But it looks like this is not an option. Now I > need to know for every incoming packet whether checksum verification should > be done or not. It should ideally be for every packet since chksum offload > can be turned off and on on the VIF and existing tcp connections should > continue. If not every packet, I need to get a notification or efficiently > detect right away that the setting is changed on the VIF. This is a question that seems to keep coming up even for Linux and Wi...

...const s_mbft * const test = addr; + + if (memcmp(test->acpi.signature, magic, sizeof magic - 1)) + return NULL; + + if (test->acpi.length != sizeof *test) + return NULL; + + { const uint8_t * const end = (void *) (test + 1); + const uint8_t * ptr; + uint8_t chksum; + + chksum = 0; + for (ptr = addr; ptr < end; ++ptr) + chksum += *ptr; + if (chksum) + return NULL; + } + + /* Looks like it's a mBFT! */ + return test; + } + +static int do_nothing(void) { + return 0; + } + +static void memdisk_info(co...

...e where the field is of type ''bytea''. This works fine if a do Base64 encoding but I just want to do character escaping. How do I do this????. What I get is this: ActiveRecord::StatementInvalid in Init_test#save_file ArgumentError: Invalid Ruby/cstring: INSERT INTO globalfiles(chksum,block,directory,filename,blocksize,time,data) VALUES(''10fcfa244eb972c6de695be235d11f98'', ''0'', ''test'', ''myfilename'', ''500000'', ''NOW()'', ''?B??H?3?!g1hV??9 blaaaahh more binary data.....

..."1.0" encoding="UTF-8" standalone="no"?> <request> <category>client</category> <action>Login</action> <params> <param name="clid">135610</param> <cltrid>135610A1276479316B171</cltrid> <chksum>4bdee845b6e6dc67754b038f2b08bf74</chksum> </params> </request> _ALTO socket=TCPSocket::new(''ip'',''port'') puts("Connect:\n"+socket.read()+"\n\n") socket.print(login_request) puts("Login:\n"+socket.read()+"\n\...

...On a monthly basis, we run with "--delete" to clean out the stale files on the hosts. The command I use daily is: "/usr/bin/rsync -a -e ssh", with a ksh for loop on the 250+ host names The version is: "rsync version 2.5.7 protocol version 26" Since rsync must do a chksum on the local and remote box on all files, the whole sync process takes over 2hrs even if nothing was changed. My questions are: 1) I know I have an old version, are there performance improvements in the later versions? I am not the SA, the process to request a new install is lengthy. 2) Is there...

This small set fixes few bugs, improves gpt handling (under buggy conditions) and implements strict flag with more fine grained control which should fix issues with sanity checks against disk sizes. If this set is allright I'd want to do what I mentioned in older discussion with Ady - backport missing patches from 6.x to 5.x and 4.x so all versions have up to date chain version. Michal

...nsigned int siz) -{ - return crc == crc32(crc32(0, NULL, 0), buf, siz); -} - -static int gpt_check_hdr_crc(const struct disk_info * const diskinfo, struct disk_gpt_header **_gh) -{ - struct disk_gpt_header *gh = *_gh; - uint64_t lba_alt; - uint32_t hold_crc32; - - hold_crc32 = gh->chksum; - gh->chksum = 0; - if (!valid_crc(hold_crc32, (const uint8_t *)gh, gh->hdr_size)) { - warn("Primary GPT header checksum invalid."); - /* retry with backup */ - lba_alt = gh->lba_alt; - free(gh); - if (!(gh = *_gh = disk_read_sectors(diskinfo, lba_alt, 1))) { - error(&...

...0/i386/) domU: kernel-PAE-2.6.31.12-174.2.3.fc12.i686.rpm xen: xen-hypervisor-3.4.2-1.fc12.i686.rpm Hardware: Pentium 4 without any virtualization support peth0: on board PCI-E Marvell Yukon 88E8053 (driver sky2) peth1: PCI Intel Pro/1000GT (driver e1000) I can reproduce this 100%. Turning off tx chksumming (eththool -K {dev} tx off) on all devices in dom0 and domU does not help. I would be happy if someone can give me a hint, if there is any fix available, either by configuration settings or replacing one of the kernels? Regards, Bernhard _______________________________________________ Xen-us...

...er > > PixBrixen# --------- PACKET --------- > > -- IP -- > eliot_gate ==> 209.67.79.132 > > ver = 0x4 hlen = 0x5 tos = 0x0 tlen = 0x3c > id = 0xbc1a flags = 0x40 frag off=0x0 > ttl = 0x3f proto=0x6 chksum = 0x4f99 > > -- TCP -- > source port = 0xaaf7 dest port = 0x1bdsyn What is this?->->->->->->->->->->->->->->->->->->->->-^^^^^^^^ Did the line breaks get messed up? If so we might have a "syn"...

...t the tar linkflag is, I am unsure how safe this is to do. Any hints or comments gratefully accepted. Peter The relevant debug messages, and code follow: ----------------------------------------------- (1) DEBUG MESSAGES ... Reading the next header ... checksum totals chk=5786 fchk=5786 chksum= 13232 firstb=805D9, secondb=A3E80, len=40 Warning: NULL link flag (gnu tar archive ?) \a\508_c_rle.ps.gz Skip = 0, cliplist=<NULL>, file=\a\508_c_rle.ps.gz Skiping file. Size = 2231512 Advancing to next block: a3e80 ... (2) CODE SNIPPETS from "clitar.c" In clitar.c the problem...

This is a bit updated set of chain.c32 changes that simplifies a few things (and in partiter part), fixes few minor issues and adds a few new features. Details are in the following commits, below is the summary and pull details at the end. Shao - any chance to peek over them ? Most of those are relatively simple changes and well tested, though of course something might have slipped my attention.

1) code split and move Iterator related functionality is yanked from chain.c and moved to iterator.{c,h}. Both are moved to com32/chain and this way chain.c is ready for further splitting. Alternatively, partiter could be moved to com32/lib at any time in the future. It's potentially useful for other modules (e.g. if someone wanted to code partition dumper or editor). 2) Iterator updates

...; structure */ + uint32_t mBFT; /* Offset from hook to the mBFT; refilled + * by setup() with the physical address + */ +} __attribute__((packed)); + /* The Disk Parameter Table may be required */ typedef union { struct hd_dpt { @@ -102,6 +115,11 @@ struct edd_dpt { uint8_t chksum; /* DPI checksum */ } __attribute__((packed)); +struct mBFT { + struct acpi_description_header acpi; + uint32_t safe_hook; /* "Safe hook" physical address */ +} __attribute__((packed)); + struct patch_area { uint32_t diskbuf; uint32_t disksize; @@ -816,6 +834,7 @@ vo...

Hi! Today I encountered data corruption on two zfs pools due to a RAM failure in my OI box running on a dell T710. My rpool now looks like this (after reboot): pool: rpool state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire

...nline int valid_crc(uint32_t crc, const uint8_t *buf, unsigned int siz) -{ - return crc == crc32(crc32(0, NULL, 0), buf, siz); -} - -static int valid_crc_gpth(struct disk_gpt_header *gh, int flags) -{ - uint32_t crc, crcc; - - if (!(flags & PIF_GPTHCRC)) - return 1; - - crc = gh->chksum; - gh->chksum = 0; - crcc = crc32(crc32(0, NULL, 0), (const uint8_t *)gh, gh->hdr_size); - gh->chksum = crc; - return crc == crcc; -} - -static int valid_crc_gptl(const struct disk_gpt_header *gh, const struct disk_gpt_part_entry *gl, int flags) -{ - uint32_t crcc; - - if...

I spent about 12 hours today writing a nice backup system based on Mike Rubel's snapshot system; but much to my dismay, when I took it for a test drive, I found that rsync hung on the first large directory I tried to back up. Aiee! A few web searches later, I realized that a lot of folks have seen this problem. I saw one proposed fix...

corrupted checksums happen all the time with the 6-port serial card, even when only using one port (and I don't give a shit about the other ports, if anybody has a one-port laying around...) so stop whining already. $OpenBSD$ --- drivers/bcmxcp_ser.c.orig Wed Aug 23 11:15:54 2006 +++ drivers/bcmxcp_ser.c Wed Aug 23 11:26:37 2006 @@ -168,8 +168,8 @@ int get_answer(unsigned char *data, unsi