Displaying 4 results from an estimated 4 matches for "mattd".
Did you mean:
matt
2013 Dec 01
70
[PATCH 00/13] Coverity fixes for libxl
Matthew Daley (13):
libxl: fix unsigned less-than-0 comparison in e820_sanitize
libxl: check for xc_domain_setmaxmem failure in libxl__build_pre
libxl: correct file open success check in libxl__device_pci_reset
libxl: don''t leak p in libxl__wait_for_backend
libxl: remove unsigned less-than-0 comparison
libxl: actually abort if initializing a ctx''s lock fails
libxl:
2013 Nov 30
7
[xen-unstable test] 22184: regressions - trouble: broken/fail/pass
...x.com>
Ian Campbell <ian.campbell@citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
Jan Beulich <jbeulich@suse.com>
Jean-Yves Migeon <jym@NetBSD.org>
Julien Grall <julien.grall@linaro.org>
Julien Grall<julien.grall@linaro.org>
Matthew Daley <mattd@bugfuzz.com>
Mukesh Rathor <mukesh.rathor@oracle.com>
Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>
Paul Durrant <paul.durrant@citrix.com>
Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Roger Pau Monné <roger.pau@citrix.com>
Stefano Stab...
2002 Nov 17
1
error message - bad hard drive?
Hi
upon booting this morning (Redhat 8.0), i received this error message
Nov 17 02:55:07 jaguar kernel: EXT3-fs error (device ide0(3,3)):
ext3_find_entry: bad entry in directory #1111941: inode out of bounds -
offset=36, inode=537868397, rec_len=12, name_len=4
I've also had these messages too
Nov 3 20:25:42 jaguar kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Nov 3
2002 Jan 06
3
puzzling error message
Hi
RedHat 7.2, ext3 on /, kernel 2.4.18p1.
whilst updatedb was running, i had these messages appear...
Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)):
ext3_readdir: bad entry in directory #147553: rec_len %% 4 != 0 -
offset=0, inode=1651076143, rec_len=19527, name_len=85
Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)):
ext3_readdir: bad entry in directory