similar to: Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60

There''s no need to preserve this abstraction; it used to let us use hardware crc32c support directly, but libcrc32c now does that for us through the crypto API -- so we''re already using the Intel crc32c acceleration where appropriate, without having to do anything special. As is right and proper. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> ---

https://bugs.freedesktop.org/show_bug.cgi?id=96836 Bug ID: 96836 Summary: Kernel unaligned access at TPC[105d9fb4] nvkm_instobj_wr32+0x14/0x20 [nouveau] Product: xorg Version: unspecified Hardware: SPARC OS: Linux (All) Status: NEW Severity: normal Priority: medium

This series adds an initial implementation for scrub. It works quite straightforward. The usermode issues an ioctl for each device in the fs. For each device, it enumerates the allocated device chunks. For each chunk, the contained extents are enumerated and the data checksums fetched. The extents are read sequentially and the checksums verified. If an error occurs (checksum or EIO), a good copy

The goal is to detect when drives start to get an increased error rate, when drives should be replaced soon. Therefore statistic counters are added that count IO errors (read, write and flush). Additionally, the software detected errors like checksum errors and corrupted blocks are counted. An ioctl interface is added to get the device statistic counters. A second ioctl is added to atomically get

Hello! First, i come from germany and my english ist not so good, but try to explain my problem. For my studium i have to programm a kernelmodule which replace the original irq-routine for the keyboarddriver. I have already compile the module an insmoded them in a domU. I used this example "http://www.faqs.org/docs/kernel/x1206.html". With pci-access to the pci/isa-bridge it seems

PCmark2005 running in Windows XP is known to need this mmio decoder. This patch also fixes some inconsistencies, the comments of mmio decoder use AT&T ordering for operands, but the syntax looks like Intel asm. This leads to much confusion. Signed-off-by: Qing He <qing.he@intel.com> Thanks, Qing _______________________________________________ Xen-devel mailing list

Hi, I receive data from our ISDN PTP Line (by T-Com, Germany) that seems to be not processed correctly by Asterisk 1.2.13-BRIstuffed-0.3.0-PRE-1w pri debug: 1 Length (57) of 0x38 component is too long 1 !! Invalid DivertingLegInformation2 component received 0x38 This only happens on calls that are forwarded to us, the packet in question seems to contain the RDNIS. I guess this needs some code

In trying to track down a weird tree log problem I wanted to make sure that the free space cache was actually valid, which we currently have no way of doing. So this patch adds a bunch of support for the free space cache code and then a checker to fsck. Basically we go through and if we can actually load the free space cache then we will walk the extent tree and verify that the free space cache

Changes v1-v2: - Remove restriction that BTRFS_IOC_GET_DEVICE_STATS is a privileged operation - Cast u64 to unsigned long long for printf() Changes v2-v3: - Rebased on Chris'' current master Changes v3-v4: - Add padding at end of ioctl structure Changes v4-v5: - The statistic members in the ioctl are now organized as an array of 64 bit values. Symbolic names for the array indexes

V1->V2: Check to see if our current ppos is >= i_size after a short DIO read, just in case it was actually a short read and we need to just return. This is similar to what already happens in the write case. If we have a short read while doing O_DIRECT, instead of just returning, fallthrough and try to read the rest via buffered IO. BTRFS needs this because if we encounter a compressed or