Error testing ext3 on brd ramdisk

Error testing ext3 on brd ramdisk

[Adrian Hunter]

Hi

I am trying to test EXT3 on a ramdisk and after some number of mounts
(anywhere from 7 to 603 so far), I get errors from e2fsck like this:

/dev/ram0: HTREE directory inode 137 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram0: Entry 'f1770' in /work/p0/da/d1c61 (137) has deleted/unused inode 692.  CLEARED.
/dev/ram0: Entry 'fa37' in /work/p0/da/d1c61 (137) has deleted/unused inode 799.  CLEARED.
/dev/ram0: Entry 'c1686' in /work/p0/da/d1c61 (137) has deleted/unused inode 470.  CLEARED.
/dev/ram0: Entry 'c19b8' in /work/p0/da/d1c61 (137) has an incorrect filetype (was 3, should be 1).

/dev/ram0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
       (i.e., without -a or -p options)


This is what I do:


modprobe brd rd_nr=1 rd_size=4096
mkfs.ext3 /dev/ram0
dmesg -n8
i=0
while (true); do
	i=`expr $i + 1`
	echo -------------------------------------------------------------
	echo Cycle $i
	date
	echo Mounting
	sleep 1
	mount -t ext3 /dev/ram0 /mnt/test_file_system || exit 1
	echo Removing old fsstress data
	rm -rf /mnt/test_file_system/work
	mkdir /mnt/test_file_system/work || exit 1
	echo Starting fsstress
	fsstress -d /mnt/test_file_system/work -p 3 -l 0 -n 100000000 &
	echo Sleeping 30 seconds
	sleep 30
	echo Stopping fsstress
	while (ps -e | grep fsstress);do
		pkill fsstress
		sleep 1
	done
	echo Unmounting
	umount /mnt/test_file_system || exit 1
	echo Checking
	sleep 1
	e2fsck -fvp /dev/ram0 || exit 1
done


It seems to happen ever since the introduction of brd (Feb '08).

Does anyone know what is going on?

Regards
Adrian

Re: Error testing ext3 on brd ramdisk

[Jorge Boncompte [DTI2]]

Adrian Hunter escribió:
> Hi
> 
> I am trying to test EXT3 on a ramdisk and after some number of mounts
> (anywhere from 7 to 603 so far), I get errors from e2fsck like this:
> 
> /dev/ram0: HTREE directory inode 137 has an invalid root node.
> HTREE INDEX CLEARED.
> /dev/ram0: Entry 'f1770' in /work/p0/da/d1c61 (137) has deleted/unused 
> inode 692.  CLEARED.
> /dev/ram0: Entry 'fa37' in /work/p0/da/d1c61 (137) has deleted/unused 
> inode 799.  CLEARED.
> /dev/ram0: Entry 'c1686' in /work/p0/da/d1c61 (137) has deleted/unused 
> inode 470.  CLEARED.
> /dev/ram0: Entry 'c19b8' in /work/p0/da/d1c61 (137) has an incorrect 
> filetype (was 3, should be 1).
> 
> /dev/ram0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
>       (i.e., without -a or -p options)
> 
> 
> This is what I do:
> 
> 
> modprobe brd rd_nr=1 rd_size=4096
> mkfs.ext3 /dev/ram0
> dmesg -n8
> i=0
> while (true); do
>     i=`expr $i + 1`
>     echo -------------------------------------------------------------
>     echo Cycle $i
>     date
>     echo Mounting
>     sleep 1
>     mount -t ext3 /dev/ram0 /mnt/test_file_system || exit 1
>     echo Removing old fsstress data
>     rm -rf /mnt/test_file_system/work
>     mkdir /mnt/test_file_system/work || exit 1
>     echo Starting fsstress
>     fsstress -d /mnt/test_file_system/work -p 3 -l 0 -n 100000000 &
>     echo Sleeping 30 seconds
>     sleep 30
>     echo Stopping fsstress
>     while (ps -e | grep fsstress);do
>         pkill fsstress
>         sleep 1
>     done
>     echo Unmounting
>     umount /mnt/test_file_system || exit 1
>     echo Checking
>     sleep 1
>     e2fsck -fvp /dev/ram0 || exit 1
> done
> 
> 
> It seems to happen ever since the introduction of brd (Feb '08).
> 
> Does anyone know what is going on?
> 
	Hi,

	I have added Nick Piggin to the CC: as maintainer of the brd driver.

	After switching an embedded distribution that /etc on a ramdisk based 
minix filesystem from 2.6.23.17 to 2.6.29-rcX i am too getting errors 
ant the filesystem is corrupted. Does not happen always. The visible 
effect with text files after reboot is getting the old version of the 
file and "\0"'s at the end.

	Did you found a solution?

	Regards,

	Jorge
-- 
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be made.
==============================================================

Re: Error testing ext3 on brd ramdisk

[Nick Piggin]

On Fri, Feb 27, 2009 at 07:08:46PM +0100, Jorge Boncompte [DTI2] wrote:
> Adrian Hunter escribió:
> >Hi
> >
> >I am trying to test EXT3 on a ramdisk and after some number of mounts
> >(anywhere from 7 to 603 so far), I get errors from e2fsck like this:
> >
> >/dev/ram0: HTREE directory inode 137 has an invalid root node.
> >HTREE INDEX CLEARED.
> >/dev/ram0: Entry 'f1770' in /work/p0/da/d1c61 (137) has deleted/unused 
> >inode 692.  CLEARED.
> >/dev/ram0: Entry 'fa37' in /work/p0/da/d1c61 (137) has deleted/unused 
> >inode 799.  CLEARED.
> >/dev/ram0: Entry 'c1686' in /work/p0/da/d1c61 (137) has deleted/unused 
> >inode 470.  CLEARED.
> >/dev/ram0: Entry 'c19b8' in /work/p0/da/d1c61 (137) has an incorrect 
> >filetype (was 3, should be 1).
> >
> >/dev/ram0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> >      (i.e., without -a or -p options)
> >
> >
> >This is what I do:
> >
> >
> >modprobe brd rd_nr=1 rd_size=4096
> >mkfs.ext3 /dev/ram0
> >dmesg -n8
> >i=0
> >while (true); do
> >    i=`expr $i + 1`
> >    echo -------------------------------------------------------------
> >    echo Cycle $i
> >    date
> >    echo Mounting
> >    sleep 1
> >    mount -t ext3 /dev/ram0 /mnt/test_file_system || exit 1
> >    echo Removing old fsstress data
> >    rm -rf /mnt/test_file_system/work
> >    mkdir /mnt/test_file_system/work || exit 1
> >    echo Starting fsstress
> >    fsstress -d /mnt/test_file_system/work -p 3 -l 0 -n 100000000 &
> >    echo Sleeping 30 seconds
> >    sleep 30
> >    echo Stopping fsstress
> >    while (ps -e | grep fsstress);do
> >        pkill fsstress
> >        sleep 1
> >    done
> >    echo Unmounting
> >    umount /mnt/test_file_system || exit 1
> >    echo Checking
> >    sleep 1
> >    e2fsck -fvp /dev/ram0 || exit 1
> >done
> >
> >
> >It seems to happen ever since the introduction of brd (Feb '08).
> >
> >Does anyone know what is going on?
> >
> 	Hi,
> 
> 	I have added Nick Piggin to the CC: as maintainer of the brd driver.
> 
> 	After switching an embedded distribution that /etc on a ramdisk 
> 	based minix filesystem from 2.6.23.17 to 2.6.29-rcX i am too getting errors 
> ant the filesystem is corrupted. Does not happen always. The visible 
> effect with text files after reboot is getting the old version of the 
> file and "\0"'s at the end.
> 
> 	Did you found a solution?

What architectures are you using? It's possible that brd is missing
a cacheflush. I test it pretty heavily on x86 and no problems, so
this might point to an arch specific problem.

---
 drivers/block/brd.c |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

Index: linux-2.6/drivers/block/brd.c
===================================================================
--- linux-2.6.orig/drivers/block/brd.c
+++ linux-2.6/drivers/block/brd.c
@@ -275,8 +275,10 @@ static int brd_do_bvec(struct brd_device
 	if (rw == READ) {
 		copy_from_brd(mem + off, brd, sector, len);
 		flush_dcache_page(page);
-	} else
+	} else {
+		flush_dcache_page(page);
 		copy_to_brd(brd, mem + off, sector, len);
+	}
 	kunmap_atomic(mem, KM_USER0);
 
 out:

Re: Error testing ext3 on brd ramdisk

[Jorge Boncompte [DTI2]]

[-- Attachment #1: Type: text/plain, Size: 2686 bytes --]

Nick Piggin escribió:
> On Fri, Feb 27, 2009 at 07:08:46PM +0100, Jorge Boncompte [DTI2] wrote:
>> 	Hi,
>>
>> 	I have added Nick Piggin to the CC: as maintainer of the brd driver.
>>
>> 	After switching an embedded distribution that /etc on a ramdisk 
>> 	based minix filesystem from 2.6.23.17 to 2.6.29-rcX i am too getting errors 
>> ant the filesystem is corrupted. Does not happen always. The visible 
>> effect with text files after reboot is getting the old version of the 
>> file and "\0"'s at the end.
>>
>> 	Did you found a solution?
> 
> What architectures are you using? It's possible that brd is missing
> a cacheflush. I test it pretty heavily on x86 and no problems, so
> this might point to an arch specific problem.
> 
> ---
>  drivers/block/brd.c |    4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> Index: linux-2.6/drivers/block/brd.c
> ===================================================================
> --- linux-2.6.orig/drivers/block/brd.c
> +++ linux-2.6/drivers/block/brd.c
> @@ -275,8 +275,10 @@ static int brd_do_bvec(struct brd_device
>  	if (rw == READ) {
>  		copy_from_brd(mem + off, brd, sector, len);
>  		flush_dcache_page(page);
> -	} else
> +	} else {
> +		flush_dcache_page(page);
>  		copy_to_brd(brd, mem + off, sector, len);
> +	}
>  	kunmap_atomic(mem, KM_USER0);
>  
>  out:

	Hi, I am on 32bits x86, 2 x Xeon with HT CPUs, but I have seen the same 
corruption on a KVM/QEMU guest with single emulated CPU.

	With your patch on top of vanilla 2.6.29-rc3+plus some networking 
patches I still get corruption sometimes.

	The script that saves the configuration does...

------------
mount -no remount,ro /dev/ram0
dd if=/dev/ram0 of=config.bin bs=1k count=1000
mount -no remount,rw /dev/ram0
md5sum config.bin
dd if=config.bin of=/dev/hda1
echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
------------

on system boot

------------
CHECK MD5SUM
dd if=/dev/hda1 of=/dev/ram0 bs=1k count=1000
fsck.minix -a /dev/ram0
mount -nt minix /dev/ram0 /etc -o rw
------------

	I have never seen a MD5 failure on boot, just sometimes the filesystem 
is corrupted. Kernel config attached.

	Jorge
-- 
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be made.
==============================================================

[-- Attachment #2: config-kernel --]
[-- Type: text/plain, Size: 62840 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.29-rc3
# Wed Feb 25 20:50:00 2009
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_GPIO=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set

#
# RCU Subsystem
#
CONFIG_CLASSIC_RCU=y
# CONFIG_TREE_RCU is not set
# CONFIG_PREEMPT_RCU is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_PREEMPT_RCU_TRACE is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=19
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_GROUP_SCHED is not set
# CONFIG_CGROUPS is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_IPC_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_NET_NS=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
CONFIG_TRACEPOINTS=y
# CONFIG_MARKERS is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_INTEGRITY is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_IOSCHED_CFQ is not set
# CONFIG_DEFAULT_AS is not set
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="deadline"
# CONFIG_FREEZER is not set

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
# CONFIG_SPARSE_IRQ is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
# CONFIG_X86_RDC321X is not set
CONFIG_SCHED_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
CONFIG_M586MMX=y
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CPU=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
# CONFIG_X86_PPRO_FENCE is not set
CONFIG_X86_F00F_BUG=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_TSC=y
CONFIG_X86_MINIMUM_CPU_FAMILY=4
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_CYRIX_32=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR_32=y
CONFIG_CPU_SUP_TRANSMETA_32=y
CONFIG_CPU_SUP_UMC_32=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
# CONFIG_IOMMU_API is not set
CONFIG_NR_CPUS=8
# CONFIG_SCHED_SMT is not set
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_X86_REBOOTFIXUPS=y
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
# CONFIG_X86_PAE is not set
# CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_PHYS_ADDR_T_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_UNEVICTABLE_LRU=y
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW_64K=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
# CONFIG_EFI is not set
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_300=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=300
CONFIG_SCHED_HRTICK=y
# CONFIG_KEXEC is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
# CONFIG_HOTPLUG_CPU is not set
CONFIG_COMPAT_VDSO=y
# CONFIG_CMDLINE_BOOL is not set

#
# Power management and ACPI options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SUSPEND is not set
# CONFIG_HIBERNATION is not set
CONFIG_ACPI=y
# CONFIG_ACPI_PROCFS is not set
# CONFIG_ACPI_PROCFS_POWER is not set
CONFIG_ACPI_SYSFS_POWER=y
# CONFIG_ACPI_PROC_EVENT is not set
CONFIG_ACPI_AC=y
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
# CONFIG_PCI_GOOLPC is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
# CONFIG_PCIEASPM is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_SCx200=m
CONFIG_SCx200HR_TIMER=m
CONFIG_GEODE_LX=y
CONFIG_GEODE_MFGPT_TIMER=y
# CONFIG_OLPC is not set
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_HAVE_AOUT=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set
CONFIG_HAVE_ATOMIC_IOMAP=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_COMPAT_NET_DEV_OPS=y
CONFIG_NET_NS_NR=1
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=m
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_MPLS=m
CONFIG_MPLS_TUNNEL=m
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_ASK_IP_FIB_HASH is not set
CONFIG_IP_FIB_TRIE=y
# CONFIG_IP_FIB_HASH is not set
# CONFIG_IP_FIB_TRIE_STATS is not set
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_IP_MPLS=m
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=m
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
# CONFIG_TCP_CONG_VEGAS is not set
# CONFIG_TCP_CONG_SCALABLE is not set
# CONFIG_TCP_CONG_LP is not set
CONFIG_TCP_CONG_VENO=m
# CONFIG_TCP_CONG_YEAH is not set
# CONFIG_TCP_CONG_ILLINOIS is not set
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
# CONFIG_BRIDGE_NETFILTER is not set

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
# CONFIG_NF_CT_ACCT is not set
CONFIG_NF_CONNTRACK_MARK=y
# CONFIG_NF_CONNTRACK_EVENTS is not set
# CONFIG_NF_CT_PROTO_DCCP is not set
CONFIG_NF_CT_PROTO_GRE=m
# CONFIG_NF_CT_PROTO_SCTP is not set
CONFIG_NF_CT_PROTO_UDPLITE=m
# CONFIG_NF_CONNTRACK_AMANDA is not set
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
# CONFIG_NF_CONNTRACK_SANE is not set
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_TPROXY=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_MPLS=m
# CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_TPROXY=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
# CONFIG_NETFILTER_XT_MATCH_CONNBYTES is not set
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
# CONFIG_NETFILTER_XT_MATCH_DCCP is not set
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
# CONFIG_NETFILTER_XT_MATCH_LIMIT is not set
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
# CONFIG_NETFILTER_XT_MATCH_SOCKET is not set
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_AH_ESP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m

#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
# CONFIG_IP_NF_TARGET_NETMAP is not set
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_PROTO_UDPLITE=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
# CONFIG_NF_NAT_AMANDA is not set
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
# CONFIG_IP_NF_ARPTABLES is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
CONFIG_ATM=y
CONFIG_ATM_CLIP=m
CONFIG_ATM_CLIP_NO_ICMP=y
# CONFIG_ATM_LANE is not set
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_ATM_OAM=m
CONFIG_STP=y
CONFIG_GARP=m
CONFIG_BRIDGE=y
CONFIG_BRIDGE_MPLS=m
# CONFIG_NET_DSA is not set
CONFIG_VLAN_8021Q=m
CONFIG_VLAN_8021Q_GVRP=y
# CONFIG_DECNET is not set
CONFIG_LLC=y
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
# CONFIG_NET_SCH_CBQ is not set
CONFIG_NET_SCH_HTB=y
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_MULTIQ=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=y
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_DRR=m
CONFIG_NET_SCH_INGRESS=y

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=y
# CONFIG_CLS_U32_PERF is not set
# CONFIG_CLS_U32_MARK is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not set
# CONFIG_NET_EMATCH is not set
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=y
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
# CONFIG_NET_ACT_NAT is not set
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
# CONFIG_NET_ACT_SKBEDIT is not set
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_PHONET is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_CFG80211=m
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_NL80211=y
CONFIG_WIRELESS_OLD_REGULATORY=y
CONFIG_WIRELESS_EXT=y
CONFIG_WIRELESS_EXT_SYSFS=y
CONFIG_LIB80211=m
CONFIG_LIB80211_CRYPT_WEP=m
CONFIG_LIB80211_CRYPT_CCMP=m
CONFIG_LIB80211_CRYPT_TKIP=m
CONFIG_MAC80211=m

#
# Rate control algorithm selection
#
CONFIG_MAC80211_RC_MINSTREL=y
# CONFIG_MAC80211_RC_DEFAULT_PID is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel"
# CONFIG_MAC80211_MESH is not set
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PNP=y
# CONFIG_PNP_DEBUG_MESSAGES is not set

#
# Protocols
#
CONFIG_ISAPNP=y
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not set
# CONFIG_C2PORT is not set

#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_93CX6 is not set
CONFIG_HAVE_IDE=y
CONFIG_IDE=y

#
# Please see Documentation/ide/ide.txt for help/info on IDE drives
#
CONFIG_IDE_TIMINGS=y
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_IDE_GD=y
CONFIG_IDE_GD_ATA=y
# CONFIG_IDE_GD_ATAPI is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEACPI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_PROC_FS is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_PLATFORM is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEDMA_SFF=y

#
# PCI IDE chipsets support
#
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_PCIBUS_ORDER is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
CONFIG_BLK_DEV_CS5520=y
CONFIG_BLK_DEV_CS5530=y
CONFIG_BLK_DEV_CS5535=y
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
CONFIG_BLK_DEV_SC1200=y
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT8172 is not set
# CONFIG_BLK_DEV_IT8213 is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_BLK_DEV_TC86C001 is not set

#
# Other IDE chipsets support
#

#
# Note: most of these also require special kernel boot parameters
#
# CONFIG_BLK_DEV_4DRIVES is not set
# CONFIG_BLK_DEV_ALI14XX is not set
# CONFIG_BLK_DEV_DTC2278 is not set
# CONFIG_BLK_DEV_HT6560B is not set
# CONFIG_BLK_DEV_QD65XX is not set
# CONFIG_BLK_DEV_UMC8672 is not set
CONFIG_BLK_DEV_IDEDMA=y

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_LIBFC is not set
# CONFIG_FCOE is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
CONFIG_SCSI_GDTH=m
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_SCSI_DH is not set
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=m
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=m
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
CONFIG_SATA_PROMISE=m
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
CONFIG_SATA_VIA=m
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ACPI is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
CONFIG_ATA_GENERIC=m
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_ISAPNP is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_QDI is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_WINBOND_VLB is not set
# CONFIG_PATA_SCH is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID10 is not set
CONFIG_MD_RAID456=y
CONFIG_MD_RAID5_RESHAPE=y
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
# CONFIG_DM_CRYPT is not set
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_MIRROR is not set
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#

#
# Enable only one of the two stacks, unless you know what you are doing
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_MACVLAN=m
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
CONFIG_VETH=m
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=y

#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_REALTEK_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
# CONFIG_FIXED_PHY is not set
# CONFIG_MDIO_BITBANG is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
# CONFIG_EL3 is not set
# CONFIG_3C515 is not set
CONFIG_VORTEX=y
CONFIG_TYPHOON=y
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=y
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
CONFIG_E100=y
# CONFIG_FEALNX is not set
CONFIG_NATSEMI=y
CONFIG_NE2K_PCI=y
CONFIG_8139CP=y
CONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_R6040 is not set
CONFIG_SIS900=y
CONFIG_EPIC100=y
# CONFIG_SMSC9420 is not set
CONFIG_SUNDANCE=y
CONFIG_SUNDANCE_MMIO=y
# CONFIG_TLAN is not set
CONFIG_VIA_RHINE=y
CONFIG_VIA_RHINE_MMIO=y
# CONFIG_SC92031 is not set
# CONFIG_NET_POCKET is not set
# CONFIG_ATL2 is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
CONFIG_DL2K=y
CONFIG_E1000=y
# CONFIG_E1000E is not set
# CONFIG_IP1000 is not set
# CONFIG_IGB is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_R8169=y
CONFIG_R8169_VLAN=y
# CONFIG_SIS190 is not set
CONFIG_SKGE=y
# CONFIG_SKGE_DEBUG is not set
CONFIG_SKY2=y
# CONFIG_SKY2_DEBUG is not set
CONFIG_VIA_VELOCITY=y
CONFIG_TIGON3=y
CONFIG_BNX2=y
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_JME is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
CONFIG_WLAN_80211=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
# CONFIG_AIRO is not set
# CONFIG_HERMES is not set
# CONFIG_ATMEL is not set
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not set
# CONFIG_ADM8211 is not set
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_P54_COMMON is not set
# CONFIG_ATH5K is not set
CONFIG_ATH9K=m
# CONFIG_ATH9K_DEBUG is not set
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_IWLCORE is not set
# CONFIG_IWLWIFI_LEDS is not set
# CONFIG_IWLAGN is not set
# CONFIG_IWL3945 is not set
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
CONFIG_HOSTAP_FIRMWARE_NVRAM=y
# CONFIG_HOSTAP_PLX is not set
CONFIG_HOSTAP_PCI=m
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_ZD1211RW is not set
# CONFIG_RT2X00 is not set

#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
CONFIG_USB_PEGASUS=m
# CONFIG_USB_RTL8150 is not set
CONFIG_USB_USBNET=m
# CONFIG_USB_NET_AX8817X is not set
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_DM9601=m
# CONFIG_USB_NET_SMSC95XX is not set
# CONFIG_USB_NET_GL620A is not set
# CONFIG_USB_NET_NET1080 is not set
# CONFIG_USB_NET_PLUSB is not set
# CONFIG_USB_NET_MCS7830 is not set
# CONFIG_USB_NET_RNDIS_HOST is not set
# CONFIG_USB_NET_CDC_SUBSET is not set
# CONFIG_USB_NET_ZAURUS is not set
CONFIG_WAN=y
# CONFIG_HOSTESS_SV11 is not set
# CONFIG_COSA is not set
# CONFIG_LANMEDIA is not set
# CONFIG_SEALEVEL_4021 is not set
CONFIG_HDLC=m
CONFIG_HDLC_RAW=m
CONFIG_HDLC_RAW_ETH=m
CONFIG_HDLC_CISCO=m
CONFIG_HDLC_FR=m
CONFIG_HDLC_PPP=m

#
# X.25/LAPB support is disabled
#
# CONFIG_PCI200SYN is not set
# CONFIG_WANXL is not set
# CONFIG_PC300TOO is not set
# CONFIG_N2 is not set
# CONFIG_C101 is not set
# CONFIG_FARSYNC is not set
# CONFIG_DSCC4 is not set
CONFIG_DLCI=m
CONFIG_DLCI_MAX=8
# CONFIG_SDLA is not set
# CONFIG_SBNI is not set
CONFIG_ATM_DRIVERS=y
CONFIG_ATM_DUMMY=m
CONFIG_ATM_TCP=m
# CONFIG_ATM_LANAI is not set
# CONFIG_ATM_ENI is not set
# CONFIG_ATM_FIRESTREAM is not set
# CONFIG_ATM_ZATM is not set
CONFIG_ATM_NICSTAR=m
CONFIG_ATM_NICSTAR_USE_SUNI=y
# CONFIG_ATM_NICSTAR_USE_IDT77105 is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_AMBASSADOR is not set
# CONFIG_ATM_HORIZON is not set
CONFIG_ATM_IA=m
# CONFIG_ATM_IA_DEBUG is not set
# CONFIG_ATM_FORE200E is not set
CONFIG_ATM_HE=m
CONFIG_ATM_HE_USE_SUNI=y
# CONFIG_ATM_SOLOS is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
# CONFIG_PPP_FILTER is not set
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_PPPOL2TP=m
# CONFIG_SLIP is not set
CONFIG_SLHC=m
# CONFIG_NET_FC is not set
CONFIG_NETCONSOLE=m
# CONFIG_NETCONSOLE_DYNAMIC is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
CONFIG_N_HDLC=m
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set
# CONFIG_NOZOMI is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=m
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_HW_RANDOM_VIA=m
# CONFIG_NVRAM is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
# CONFIG_MWAVE is not set
CONFIG_SCx200_GPIO=m
# CONFIG_PC8736x_GPIO is not set
CONFIG_NSC_GPIO=m
CONFIG_CS5535_GPIO=m
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=m

#
# I2C Hardware Bus support
#

#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
CONFIG_I2C_I801=m
# CONFIG_I2C_ISCH is not set
CONFIG_I2C_PIIX4=m
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_SIMTEC is not set

#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set

#
# Graphics adapter I2C/DDC channel drivers
#
# CONFIG_I2C_VOODOO3 is not set

#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_PCA_ISA is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_STUB is not set
# CONFIG_SCx200_I2C is not set
CONFIG_SCx200_ACB=m

#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_PCF8575 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
# CONFIG_SPI is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
CONFIG_GPIOLIB=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set

#
# Memory mapped GPIO expanders:
#

#
# I2C GPIO expanders:
#
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set

#
# PCI GPIO expanders:
#

#
# SPI GPIO expanders:
#
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_BATTERY_BQ27x00 is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7473 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
CONFIG_SENSORS_CORETEMP=m
# CONFIG_SENSORS_IBMAEM is not set
# CONFIG_SENSORS_IBMPEX is not set
CONFIG_SENSORS_IT87=m
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
CONFIG_SENSORS_LM77=m
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
CONFIG_SENSORS_LM90=m
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_THMC50 is not set
CONFIG_SENSORS_VIA686A=m
# CONFIG_SENSORS_VT1211 is not set
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
CONFIG_SENSORS_W83L785TS=m
# CONFIG_SENSORS_W83L786NG is not set
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_SENSORS_LIS3LV02D is not set
# CONFIG_SENSORS_APPLESMC is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
CONFIG_THERMAL=y
# CONFIG_THERMAL_HWMON is not set
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
CONFIG_GEODE_WDT=m
CONFIG_SC520_WDT=m
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_IBMASR is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not set
CONFIG_ITCO_WDT=m
CONFIG_ITCO_VENDOR_SUPPORT=y
CONFIG_IT8712F_WDT=m
# CONFIG_IT87_WDT is not set
# CONFIG_HP_WATCHDOG is not set
# CONFIG_SC1200_WDT is not set
CONFIG_SCx200_WDT=m
# CONFIG_PC87413_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_SBC7240_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_SMSC_SCH311X_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
CONFIG_W83627HF_WDT=m
# CONFIG_W83697HF_WDT is not set
# CONFIG_W83697UG_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SBC_EPX_C3_WATCHDOG is not set

#
# ISA-based Watchdog Cards
#
# CONFIG_PCWATCHDOG is not set
# CONFIG_MIXCOMWD is not set
# CONFIG_WDT is not set

#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set

#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_TPS65010 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_REGULATOR is not set

#
# Multimedia devices
#

#
# Multimedia core support
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_COMMON=m
# CONFIG_VIDEO_ALLOW_V4L1 is not set
CONFIG_VIDEO_V4L1_COMPAT=y
# CONFIG_DVB_CORE is not set
CONFIG_VIDEO_MEDIA=m

#
# Multimedia drivers
#
# CONFIG_MEDIA_ATTACH is not set
CONFIG_MEDIA_TUNER=m
CONFIG_MEDIA_TUNER_CUSTOMIZE=y
# CONFIG_MEDIA_TUNER_SIMPLE is not set
# CONFIG_MEDIA_TUNER_TDA8290 is not set
# CONFIG_MEDIA_TUNER_TDA827X is not set
# CONFIG_MEDIA_TUNER_TDA18271 is not set
# CONFIG_MEDIA_TUNER_TDA9887 is not set
# CONFIG_MEDIA_TUNER_TEA5761 is not set
# CONFIG_MEDIA_TUNER_TEA5767 is not set
# CONFIG_MEDIA_TUNER_MT20XX is not set
# CONFIG_MEDIA_TUNER_MT2060 is not set
# CONFIG_MEDIA_TUNER_MT2266 is not set
# CONFIG_MEDIA_TUNER_MT2131 is not set
# CONFIG_MEDIA_TUNER_QT1010 is not set
# CONFIG_MEDIA_TUNER_XC2028 is not set
# CONFIG_MEDIA_TUNER_XC5000 is not set
# CONFIG_MEDIA_TUNER_MXL5005S is not set
# CONFIG_MEDIA_TUNER_MXL5007T is not set
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEOBUF_VMALLOC=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
# CONFIG_VIDEO_HELPER_CHIPS_AUTO is not set
# CONFIG_VIDEO_IR_I2C is not set

#
# Encoders/decoders and other helper chips
#

#
# Audio decoders
#
# CONFIG_VIDEO_TVAUDIO is not set
# CONFIG_VIDEO_TDA7432 is not set
# CONFIG_VIDEO_TDA9840 is not set
# CONFIG_VIDEO_TDA9875 is not set
# CONFIG_VIDEO_TEA6415C is not set
# CONFIG_VIDEO_TEA6420 is not set
# CONFIG_VIDEO_MSP3400 is not set
# CONFIG_VIDEO_CS5345 is not set
# CONFIG_VIDEO_CS53L32A is not set
# CONFIG_VIDEO_M52790 is not set
# CONFIG_VIDEO_TLV320AIC23B is not set
# CONFIG_VIDEO_WM8775 is not set
# CONFIG_VIDEO_WM8739 is not set
# CONFIG_VIDEO_VP27SMPX is not set

#
# Video decoders
#
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_TCM825X is not set
# CONFIG_VIDEO_SAA711X is not set
# CONFIG_VIDEO_SAA717X is not set
# CONFIG_VIDEO_TVP514X is not set
# CONFIG_VIDEO_TVP5150 is not set

#
# Video and audio decoders
#
# CONFIG_VIDEO_CX25840 is not set

#
# MPEG video encoders
#
# CONFIG_VIDEO_CX2341X is not set

#
# Video encoders
#
# CONFIG_VIDEO_SAA7127 is not set

#
# Video improvement chips
#
# CONFIG_VIDEO_UPD64031A is not set
# CONFIG_VIDEO_UPD64083 is not set
CONFIG_VIDEO_VIVI=m
CONFIG_VIDEO_BT848=m
# CONFIG_VIDEO_SAA6588 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_IVTV is not set
# CONFIG_VIDEO_CAFE_CCIC is not set
# CONFIG_SOC_CAMERA is not set
# CONFIG_V4L_USB_DRIVERS is not set
# CONFIG_RADIO_ADAPTERS is not set
# CONFIG_DAB is not set

#
# Graphics support
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
CONFIG_USB_MON=m
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_WHCI_HCD is not set
# CONFIG_USB_HWA_HCD is not set

#
# Enable Host or Gadget support to see Inventra options
#

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed;
#

#
# see USB_STORAGE Help for more information
#
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
CONFIG_USB_SERIAL=m
# CONFIG_USB_EZUSB is not set
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_CH341 is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP2101 is not set
CONFIG_USB_SERIAL_CYPRESS_M8=m
# CONFIG_USB_SERIAL_EMPEG is not set
CONFIG_USB_SERIAL_FTDI_SIO=m
# CONFIG_USB_SERIAL_FUNSOFT is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_IUU is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_MOTOROLA is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_SPCP8X5 is not set
# CONFIG_USB_SERIAL_HP4X is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIEMENS_MPI is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_OPTICON is not set
# CONFIG_USB_SERIAL_DEBUG is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_VST is not set
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m
# CONFIG_USB_GADGET is not set

#
# OTG and related infrastructure
#
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m

#
# LED drivers
#
# CONFIG_LEDS_NET48XX is not set
CONFIG_LEDS_WRAP=m
CONFIG_LEDS_ALIX2=m
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not set
# CONFIG_LEDS_CLEVO_MAIL is not set
# CONFIG_LEDS_PCA955X is not set

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
# CONFIG_LEDS_TRIGGER_IDE_DISK is not set
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
CONFIG_LEDS_TRIGGER_BACKLIGHT=m
CONFIG_LEDS_TRIGGER_DEFAULT_ON=m
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=y
CONFIG_EDAC_AMD76X=m
CONFIG_EDAC_E7XXX=m
CONFIG_EDAC_E752X=m
# CONFIG_EDAC_I82875P is not set
# CONFIG_EDAC_I82975X is not set
# CONFIG_EDAC_I3000 is not set
# CONFIG_EDAC_X38 is not set
# CONFIG_EDAC_I5400 is not set
# CONFIG_EDAC_I82860 is not set
# CONFIG_EDAC_R82600 is not set
# CONFIG_EDAC_I5000 is not set
# CONFIG_EDAC_I5100 is not set
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set

#
# SPI RTC drivers
#

#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=m
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_V3020 is not set

#
# on-CPU RTC drivers
#
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
# CONFIG_STAGING is not set
# CONFIG_X86_PLATFORM_DEVICES is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
# CONFIG_ISCSI_IBFT_FIND is not set

#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
# CONFIG_EXT4_FS is not set
CONFIG_FS_XIP=y
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=m
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=y
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
CONFIG_MINIX_FS=y
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m
# CONFIG_DLM is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC=y
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=1
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
CONFIG_DEBUG_OBJECTS=y
# CONFIG_DEBUG_OBJECTS_SELFTEST is not set
CONFIG_DEBUG_OBJECTS_FREE=y
CONFIG_DEBUG_OBJECTS_TIMERS=y
CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_PI_LIST=y
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_PROVE_LOCKING=y
CONFIG_LOCKDEP=y
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_LOCKDEP is not set
CONFIG_TRACE_IRQFLAGS=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_VM=y
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_DEBUG_LIST=y
CONFIG_DEBUG_SG=y
CONFIG_DEBUG_NOTIFIERS=y
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_RING_BUFFER=y
CONFIG_TRACING=y

#
# Tracers
#
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_CONTEXT_SWITCH_TRACER is not set
# CONFIG_BOOT_TRACER is not set
# CONFIG_TRACE_BRANCH_PROFILING is not set
# CONFIG_POWER_TRACER is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DYNAMIC_PRINTK_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_STRICT_DEVMEM is not set
# CONFIG_X86_VERBOSE_BOOTUP is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_4KSTACKS is not set
CONFIG_DOUBLEFAULT=y
CONFIG_MMIOTRACE=y
# CONFIG_MMIOTRACE_TEST is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
# CONFIG_OPTIMIZE_INLINING is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_XOR_BLOCKS=y
CONFIG_ASYNC_CORE=y
CONFIG_ASYNC_MEMCPY=y
CONFIG_ASYNC_XOR=y
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_MANAGER=m
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=m
# CONFIG_CRYPTO_TEST is not set

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set

#
# Block modes
#
CONFIG_CRYPTO_CBC=m
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=m
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=m
# CONFIG_CRYPTO_XCBC is not set

#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CRC32C_INTEL is not set
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=m
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
# CONFIG_CRYPTO_ANUBIS is not set
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_BLOWFISH=m
# CONFIG_CRYPTO_CAMELLIA is not set
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DES=m
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_586 is not set
# CONFIG_CRYPTO_SEED is not set
CONFIG_CRYPTO_SERPENT=m
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 is not set

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_LZO=m

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_PADLOCK is not set
CONFIG_CRYPTO_DEV_GEODE=m
CONFIG_CRYPTO_DEV_HIFN_795X=m
CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y
CONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=y
# CONFIG_CRC16 is not set
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=m
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

Re: Error testing ext3 on brd ramdisk

[Nick Piggin]

On Mon, Mar 02, 2009 at 06:42:18PM +0100, Jorge Boncompte [DTI2] wrote:
> Nick Piggin escribió:
> >On Fri, Feb 27, 2009 at 07:08:46PM +0100, Jorge Boncompte [DTI2] wrote:
> >>	Hi,
> >>
> >>	I have added Nick Piggin to the CC: as maintainer of the brd driver.
> >>
> >>	After switching an embedded distribution that /etc on a ramdisk 
> >>	based minix filesystem from 2.6.23.17 to 2.6.29-rcX i am too getting 
> >>	errors ant the filesystem is corrupted. Does not happen always. The 
> >>visible effect with text files after reboot is getting the old version of 
> >>the file and "\0"'s at the end.
> >>
> >>	Did you found a solution?
> >
> >What architectures are you using? It's possible that brd is missing
> >a cacheflush. I test it pretty heavily on x86 and no problems, so
> >this might point to an arch specific problem.
> >
> >---
> > drivers/block/brd.c |    4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> >Index: linux-2.6/drivers/block/brd.c
> >===================================================================
> >--- linux-2.6.orig/drivers/block/brd.c
> >+++ linux-2.6/drivers/block/brd.c
> >@@ -275,8 +275,10 @@ static int brd_do_bvec(struct brd_device
> > 	if (rw == READ) {
> > 		copy_from_brd(mem + off, brd, sector, len);
> > 		flush_dcache_page(page);
> >-	} else
> >+	} else {
> >+		flush_dcache_page(page);
> > 		copy_to_brd(brd, mem + off, sector, len);
> >+	}
> > 	kunmap_atomic(mem, KM_USER0);
> > 
> > out:
> 
> 	Hi, I am on 32bits x86, 2 x Xeon with HT CPUs, but I have seen the 
> 	same corruption on a KVM/QEMU guest with single emulated CPU.
> 
> 	With your patch on top of vanilla 2.6.29-rc3+plus some networking 
> patches I still get corruption sometimes.
> 
> 	The script that saves the configuration does...
> 
> ------------
> mount -no remount,ro /dev/ram0
> dd if=/dev/ram0 of=config.bin bs=1k count=1000
> mount -no remount,rw /dev/ram0
> md5sum config.bin
> dd if=config.bin of=/dev/hda1
> echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
> ------------
> 
> on system boot
> 
> ------------
> CHECK MD5SUM
> dd if=/dev/hda1 of=/dev/ram0 bs=1k count=1000
> fsck.minix -a /dev/ram0
> mount -nt minix /dev/ram0 /etc -o rw
> ------------
> 
> 	I have never seen a MD5 failure on boot, just sometimes the 
> 	filesystem is corrupted. Kernel config attached.

Hi Jorge,

Well I found and fixed something :) (see other mail) but I don't know
whether that applies to you here if you're running with a single CPU
and no preemption. But still, it might be worth trying that patch? I'm
sorry I'm still unable to reproduce a problem with your script
(although you don't describe how you create the filesystem before
you remount it).

>From your description, it suggests that the corrupted image is being
read from /dev/ram0 (becuase the md5sum passes).

In your script, can you run fsck.minix on config.bin when you first
create it? What if you unmount /dev/ram0 before copying the image?

Thanks,
Nick

Re: Error testing ext3 on brd ramdisk

[Jorge Boncompte [DTI2]]

Nick Piggin escribió:
> On Mon, Mar 02, 2009 at 06:42:18PM +0100, Jorge Boncompte [DTI2] wrote:
>> Nick Piggin escribió:
>>> On Fri, Feb 27, 2009 at 07:08:46PM +0100, Jorge Boncompte [DTI2] wrote:
>>>> 	Hi,
>>>>
>>>> 	I have added Nick Piggin to the CC: as maintainer of the brd driver.
>>>>
>>>> 	After switching an embedded distribution that /etc on a ramdisk 
>>>> 	based minix filesystem from 2.6.23.17 to 2.6.29-rcX i am too getting 
>>>> 	errors ant the filesystem is corrupted. Does not happen always. The 
>>>> visible effect with text files after reboot is getting the old version of 
>>>> the file and "\0"'s at the end.
>>>>
>>>> 	Did you found a solution?
>>> What architectures are you using? It's possible that brd is missing
>>> a cacheflush. I test it pretty heavily on x86 and no problems, so
>>> this might point to an arch specific problem.
>>>
>>> ---
>>> drivers/block/brd.c |    4 +++-
>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> Index: linux-2.6/drivers/block/brd.c
>>> ===================================================================
>>> --- linux-2.6.orig/drivers/block/brd.c
>>> +++ linux-2.6/drivers/block/brd.c
>>> @@ -275,8 +275,10 @@ static int brd_do_bvec(struct brd_device
>>> 	if (rw == READ) {
>>> 		copy_from_brd(mem + off, brd, sector, len);
>>> 		flush_dcache_page(page);
>>> -	} else
>>> +	} else {
>>> +		flush_dcache_page(page);
>>> 		copy_to_brd(brd, mem + off, sector, len);
>>> +	}
>>> 	kunmap_atomic(mem, KM_USER0);
>>>
>>> out:
>> 	Hi, I am on 32bits x86, 2 x Xeon with HT CPUs, but I have seen the 
>> 	same corruption on a KVM/QEMU guest with single emulated CPU.
>>
>> 	With your patch on top of vanilla 2.6.29-rc3+plus some networking 
>> patches I still get corruption sometimes.
>>
>> 	The script that saves the configuration does...
>>
>> ------------
>> mount -no remount,ro /dev/ram0
>> dd if=/dev/ram0 of=config.bin bs=1k count=1000
>> mount -no remount,rw /dev/ram0
>> md5sum config.bin
>> dd if=config.bin of=/dev/hda1
>> echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
>> ------------
>>
>> on system boot
>>
>> ------------
>> CHECK MD5SUM
>> dd if=/dev/hda1 of=/dev/ram0 bs=1k count=1000
>> fsck.minix -a /dev/ram0
>> mount -nt minix /dev/ram0 /etc -o rw
>> ------------
>>
>> 	I have never seen a MD5 failure on boot, just sometimes the 
>> 	filesystem is corrupted. Kernel config attached.
> 
> Hi Jorge,
> 
> Well I found and fixed something :) (see other mail) but I don't know
> whether that applies to you here if you're running with a single CPU
> and no preemption. But still, it might be worth trying that patch? I'm

	I first saw the corruption on the 2 x Xeon system. I'll try it and let 
you know.

> sorry I'm still unable to reproduce a problem with your script
> (although you don't describe how you create the filesystem before
> you remount it).

	If the MD5Sum check fails the startup script copy a templated image of 
the filesystem contained on a file on another partition to the ramdisk.

>>From your description, it suggests that the corrupted image is being
> read from /dev/ram0 (becuase the md5sum passes).

	No, it is read from /dev/hda1.

> In your script, can you run fsck.minix on config.bin when you first
> create it? What if you unmount /dev/ram0 before copying the image?

	Yesterday I did some tests and found that doing...

-----------
umount /etc (/etc is what is mounted from /dev/ram0)
dd if=/dev/zero of=/dev/ram0 bs=1k count=1000
mount /dev/ram0 /etc -t minix -o rw
-----------
...succeds and mounts a corrupted filesystem with the old content. Doing 
the same with the all ramdisk driver fails on mount with "no filesystem 
found".

If I do...
-----------
umount /etc (/etc is what is mounted from /dev/ram0)
echo 3 > /proc/sys/vm/drop_caches
dd if=/dev/zero of=/dev/ram0 bs=1k count=1000
mount /dev/ram0 /etc -t minix -o rw
----------
... then the mount fails with no filesystem found as it should.

	Does this ring any bell? :-)

	Regards,

	Jorge

-- 
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be made.
==============================================================

Re: Error testing ext3 on brd ramdisk

[Nick Piggin]

On Thu, Mar 05, 2009 at 10:19:46AM +0100, Jorge Boncompte [DTI2] wrote:
> Nick Piggin escribió:
> >>------------
> >>mount -no remount,ro /dev/ram0
> >>dd if=/dev/ram0 of=config.bin bs=1k count=1000
> >>mount -no remount,rw /dev/ram0
> >>md5sum config.bin
> >>dd if=config.bin of=/dev/hda1
> >>echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
> >>------------
> >>
> >>on system boot
> >>
> >>------------
> >>CHECK MD5SUM
> >>dd if=/dev/hda1 of=/dev/ram0 bs=1k count=1000
> >>fsck.minix -a /dev/ram0
> >>mount -nt minix /dev/ram0 /etc -o rw
> >>------------
> >>
> >>	I have never seen a MD5 failure on boot, just sometimes the 
> >>	filesystem is corrupted. Kernel config attached.
> >
> >>From your description, it suggests that the corrupted image is being
> >read from /dev/ram0 (becuase the md5sum passes).
> 
> 	No, it is read from /dev/hda1.

No I mean when it is first read from /dev/ram0 when you create the
image. Can you put some fsx.minix checks on the image file to try
to narrow down when exactly it is getting corrupted?


> >In your script, can you run fsck.minix on config.bin when you first
> >create it? What if you unmount /dev/ram0 before copying the image?
> 
> 	Yesterday I did some tests and found that doing...
> 
> -----------
> umount /etc (/etc is what is mounted from /dev/ram0)
> dd if=/dev/zero of=/dev/ram0 bs=1k count=1000
> mount /dev/ram0 /etc -t minix -o rw
> -----------
> ...succeds and mounts a corrupted filesystem with the old content. Doing 
> the same with the all ramdisk driver fails on mount with "no filesystem 
> found".
> 
> If I do...
> -----------
> umount /etc (/etc is what is mounted from /dev/ram0)
> echo 3 > /proc/sys/vm/drop_caches
> dd if=/dev/zero of=/dev/ram0 bs=1k count=1000
> mount /dev/ram0 /etc -t minix -o rw
> ----------
> ... then the mount fails with no filesystem found as it should.
> 
> 	Does this ring any bell? :-)

Humph. It seems like a problem with the buffercache layer rather
than brd itself. I'll dig some more.

Re: Error testing ext3 on brd ramdisk

[Jorge Boncompte [DTI2]]

Nick Piggin escribió:
> On Thu, Mar 05, 2009 at 10:19:46AM +0100, Jorge Boncompte [DTI2] wrote:
>> Nick Piggin escribió:
>>>> ------------
>>>> mount -no remount,ro /dev/ram0
>>>> dd if=/dev/ram0 of=config.bin bs=1k count=1000
>>>> mount -no remount,rw /dev/ram0
>>>> md5sum config.bin
>>>> dd if=config.bin of=/dev/hda1
>>>> echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
>>>> ------------
>>>>
>>>> on system boot
>>>>
>>>> ------------
>>>> CHECK MD5SUM
>>>> dd if=/dev/hda1 of=/dev/ram0 bs=1k count=1000
>>>> fsck.minix -a /dev/ram0
>>>> mount -nt minix /dev/ram0 /etc -o rw
>>>> ------------
>>>>
>>>> 	I have never seen a MD5 failure on boot, just sometimes the 
>>>> 	filesystem is corrupted. Kernel config attached.
>>> >From your description, it suggests that the corrupted image is being
>>> read from /dev/ram0 (becuase the md5sum passes).
>> 	No, it is read from /dev/hda1.
> 
> No I mean when it is first read from /dev/ram0 when you create the
> image. Can you put some fsx.minix checks on the image file to try
> to narrow down when exactly it is getting corrupted?

Ok. I have modified the script to do...
------------
mount -no remount,ro /dev/ram0
dd if=/dev/ram0 of=/tmp/config.bin bs=1k count=1000
fsck.minix -fv /tmp/config.bin
if [ $? != 0 ]; then
	echo "FATAL: Filesystem is corrupted"
	exit 2
fi
mount -no remount,rw /dev/ram0
md5sum config.bin
dd if=config.bin of=/dev/hda1
echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
------------
... after some cycles of modifying files on the filesystem and trying to 
save it to disk...
------------------
fsck.minix: BusyBox v1.8.2 (2008-12-03 14:24:56 CET)
Forcing filesystem check on /tmp/config.bin
Unused inode 198 is marked as 'used' in the bitmap.
Zone 393 is marked 'in use', but no file uses it.
Zone 394 is marked 'in use', but no file uses it.

    198 inodes used (58%)
    395 zones used (39%)

    163 regular files
     24 directories
      0 character device files
      0 block device files
      0 links
     10 symbolic links
------
    197 files
FATAL: Filesystem is corrupted
-------------------

-- 
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be made.
==============================================================

Re: Error testing ext3 on brd ramdisk

[Jorge Boncompte [DTI2]]

Jorge Boncompte [DTI2] escribió:
> Nick Piggin escribió:
>> On Thu, Mar 05, 2009 at 10:19:46AM +0100, Jorge Boncompte [DTI2] wrote:
>>> Nick Piggin escribió:
>>>>> ------------
>>>>> mount -no remount,ro /dev/ram0
>>>>> dd if=/dev/ram0 of=config.bin bs=1k count=1000
>>>>> mount -no remount,rw /dev/ram0
>>>>> md5sum config.bin
>>>>> dd if=config.bin of=/dev/hda1
>>>>> echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
>>>>> ------------
>>>>>
>>>>> on system boot
>>>>>
>>>>> ------------
>>>>> CHECK MD5SUM
>>>>> dd if=/dev/hda1 of=/dev/ram0 bs=1k count=1000
>>>>> fsck.minix -a /dev/ram0
>>>>> mount -nt minix /dev/ram0 /etc -o rw
>>>>> ------------
>>>>>
>>>>>     I have never seen a MD5 failure on boot, just sometimes the 
>>>>>     filesystem is corrupted. Kernel config attached.
>>>> >From your description, it suggests that the corrupted image is being
>>>> read from /dev/ram0 (becuase the md5sum passes).
>>>     No, it is read from /dev/hda1.
>>
>> No I mean when it is first read from /dev/ram0 when you create the
>> image. Can you put some fsx.minix checks on the image file to try
>> to narrow down when exactly it is getting corrupted?
> 
> Ok. I have modified the script to do...
> ------------
> mount -no remount,ro /dev/ram0
> dd if=/dev/ram0 of=/tmp/config.bin bs=1k count=1000
> fsck.minix -fv /tmp/config.bin
> if [ $? != 0 ]; then
>     echo "FATAL: Filesystem is corrupted"
>     exit 2
> fi
> mount -no remount,rw /dev/ram0
> md5sum config.bin
> dd if=config.bin of=/dev/hda1
> echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
> ------------
> ... after some cycles of modifying files on the filesystem and trying to 
> save it to disk...
> ------------------
> fsck.minix: BusyBox v1.8.2 (2008-12-03 14:24:56 CET)
> Forcing filesystem check on /tmp/config.bin
> Unused inode 198 is marked as 'used' in the bitmap.
> Zone 393 is marked 'in use', but no file uses it.
> Zone 394 is marked 'in use', but no file uses it.
> 
>    198 inodes used (58%)
>    395 zones used (39%)
> 
>    163 regular files
>     24 directories
>      0 character device files
>      0 block device files
>      0 links
>     10 symbolic links
> ------
>    197 files
> FATAL: Filesystem is corrupted
> -------------------
> 

	If after getting the "FATAL: Filesystem is corrupted" message I do 
"echo 3 > /proc/sys/vm/drop_caches" and rerun the script the filesystem 
somehow got magically fixed (I mean fsck.minix does not report errors 
and the image gets written to disk well ;-)

-- 
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be made.
==============================================================

Re: Error testing ext3 on brd ramdisk

[Nick Piggin]

On Thu, Mar 05, 2009 at 01:12:25PM +0100, Jorge Boncompte [DTI2] wrote:
> Jorge Boncompte [DTI2] escribió:
> >Ok. I have modified the script to do...
> >------------
> >mount -no remount,ro /dev/ram0
> >dd if=/dev/ram0 of=/tmp/config.bin bs=1k count=1000
> >fsck.minix -fv /tmp/config.bin
> >if [ $? != 0 ]; then
> >    echo "FATAL: Filesystem is corrupted"
> >    exit 2
> >fi
> >mount -no remount,rw /dev/ram0
> >md5sum config.bin
> >dd if=config.bin of=/dev/hda1
> >echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
> >------------
> >... after some cycles of modifying files on the filesystem and trying to 
> >save it to disk...
> >------------------
> >fsck.minix: BusyBox v1.8.2 (2008-12-03 14:24:56 CET)
> >Forcing filesystem check on /tmp/config.bin
> >Unused inode 198 is marked as 'used' in the bitmap.
> >Zone 393 is marked 'in use', but no file uses it.
> >Zone 394 is marked 'in use', but no file uses it.
> >
> >   198 inodes used (58%)
> >   395 zones used (39%)
> >
> >   163 regular files
> >    24 directories
> >     0 character device files
> >     0 block device files
> >     0 links
> >    10 symbolic links
> >------
> >   197 files
> >FATAL: Filesystem is corrupted
> >-------------------
> >
> 
> 	If after getting the "FATAL: Filesystem is corrupted" message I do 
> "echo 3 > /proc/sys/vm/drop_caches" and rerun the script the filesystem 
> somehow got magically fixed (I mean fsck.minix does not report errors 
> and the image gets written to disk well ;-)

OK, I can reproduce this. It really does seem to be due to buffercache
going out of coherency for some reason, so the trick is that you have
to fsck it while you have it mounted ro before remounting rw then modifying
it then remounting ro and fscking again (the first fsck must bring in
uptodate buffercache, and something is not being correctly invalidated).

It is also not brd or minix specific -- I reproduced it with loop driver
and ext2 too, and probably regular disk driver will have the same problem
(ie. it is something in the buffercache).

I don't know if this is the same problem as the ext3 issue -- the recipe
for reproducing ext3 problem includes umount, which will invalidate all
the buffercache unless something is holding the bdev open. But anyway I
am making some progress with this problem so I will try solve it first.

I can't think of any good reason why buffercache should be going out of
sync here...

Re: Error testing ext3 on brd ramdisk

[Nick Piggin]

On Tue, Mar 10, 2009 at 05:12:47PM +0100, Nick Piggin wrote:
> On Thu, Mar 05, 2009 at 01:12:25PM +0100, Jorge Boncompte [DTI2] wrote:
> > Jorge Boncompte [DTI2] escribió:
> > >Ok. I have modified the script to do...
> > >------------
> > >mount -no remount,ro /dev/ram0
> > >dd if=/dev/ram0 of=/tmp/config.bin bs=1k count=1000
> > >fsck.minix -fv /tmp/config.bin
> > >if [ $? != 0 ]; then
> > >    echo "FATAL: Filesystem is corrupted"
> > >    exit 2
> > >fi
> > >mount -no remount,rw /dev/ram0
> > >md5sum config.bin
> > >dd if=config.bin of=/dev/hda1
> > >echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
> > >------------
> > >... after some cycles of modifying files on the filesystem and trying to 
> > >save it to disk...
> > >------------------
> > >fsck.minix: BusyBox v1.8.2 (2008-12-03 14:24:56 CET)
> > >Forcing filesystem check on /tmp/config.bin
> > >Unused inode 198 is marked as 'used' in the bitmap.
> > >Zone 393 is marked 'in use', but no file uses it.
> > >Zone 394 is marked 'in use', but no file uses it.
> > >
> > >   198 inodes used (58%)
> > >   395 zones used (39%)
> > >
> > >   163 regular files
> > >    24 directories
> > >     0 character device files
> > >     0 block device files
> > >     0 links
> > >    10 symbolic links
> > >------
> > >   197 files
> > >FATAL: Filesystem is corrupted
> > >-------------------
> > >
> > 
> > 	If after getting the "FATAL: Filesystem is corrupted" message I do 
> > "echo 3 > /proc/sys/vm/drop_caches" and rerun the script the filesystem 
> > somehow got magically fixed (I mean fsck.minix does not report errors 
> > and the image gets written to disk well ;-)
> 
> OK, I can reproduce this. It really does seem to be due to buffercache
> going out of coherency for some reason, so the trick is that you have
> to fsck it while you have it mounted ro before remounting rw then modifying
> it then remounting ro and fscking again (the first fsck must bring in
> uptodate buffercache, and something is not being correctly invalidated).
> 
> It is also not brd or minix specific -- I reproduced it with loop driver
> and ext2 too, and probably regular disk driver will have the same problem
> (ie. it is something in the buffercache).
> 
> I don't know if this is the same problem as the ext3 issue -- the recipe
> for reproducing ext3 problem includes umount, which will invalidate all
> the buffercache unless something is holding the bdev open. But anyway I
> am making some progress with this problem so I will try solve it first.
> 
> I can't think of any good reason why buffercache should be going out of
> sync here...

Ah, of course, it would be due to directory-in-pagecache. You need
the following patch if you expect this to work.

And that confirms the ext3 problem is a different one because it
doesn't use directory in pagecache I think. Well, I'll look at
that one tomorrow.

Thanks,
Nick

---
 fs/super.c |    2 ++
 1 file changed, 2 insertions(+)

Index: linux-2.6/fs/super.c
===================================================================
--- linux-2.6.orig/fs/super.c
+++ linux-2.6/fs/super.c
@@ -644,6 +644,8 @@ int do_remount_sb(struct super_block *sb
 		acct_auto_close(sb);
 	shrink_dcache_sb(sb);
 	fsync_super(sb);
+	if (flags & MS_RDONLY)
+		invalidate_bdev(sb->s_bdev);
 
 	/* If we are remounting RDONLY and current sb is read/write,
 	   make sure there are no rw files opened */

Re: Error testing ext3 on brd ramdisk

[Jorge Boncompte [DTI2]]

Nick Piggin escribió:
> On Tue, Mar 10, 2009 at 05:12:47PM +0100, Nick Piggin wrote:
>> On Thu, Mar 05, 2009 at 01:12:25PM +0100, Jorge Boncompte [DTI2] wrote:
>>> Jorge Boncompte [DTI2] escribió:
>>>> Ok. I have modified the script to do...
>>>> ------------
>>>> mount -no remount,ro /dev/ram0
>>>> dd if=/dev/ram0 of=/tmp/config.bin bs=1k count=1000
>>>> fsck.minix -fv /tmp/config.bin
>>>> if [ $? != 0 ]; then
>>>>    echo "FATAL: Filesystem is corrupted"
>>>>    exit 2
>>>> fi
>>>> mount -no remount,rw /dev/ram0
>>>> md5sum config.bin
>>>> dd if=config.bin of=/dev/hda1
>>>> echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
>>>> ------------
>>>> ... after some cycles of modifying files on the filesystem and trying to 
>>>> save it to disk...
>>>> ------------------
>>>> fsck.minix: BusyBox v1.8.2 (2008-12-03 14:24:56 CET)
>>>> Forcing filesystem check on /tmp/config.bin
>>>> Unused inode 198 is marked as 'used' in the bitmap.
>>>> Zone 393 is marked 'in use', but no file uses it.
>>>> Zone 394 is marked 'in use', but no file uses it.
>>>>
>>>>   198 inodes used (58%)
>>>>   395 zones used (39%)
>>>>
>>>>   163 regular files
>>>>    24 directories
>>>>     0 character device files
>>>>     0 block device files
>>>>     0 links
>>>>    10 symbolic links
>>>> ------
>>>>   197 files
>>>> FATAL: Filesystem is corrupted
>>>> -------------------
>>>>
>>> 	If after getting the "FATAL: Filesystem is corrupted" message I do 
>>> "echo 3 > /proc/sys/vm/drop_caches" and rerun the script the filesystem 
>>> somehow got magically fixed (I mean fsck.minix does not report errors 
>>> and the image gets written to disk well ;-)
>> OK, I can reproduce this. It really does seem to be due to buffercache
>> going out of coherency for some reason, so the trick is that you have
>> to fsck it while you have it mounted ro before remounting rw then modifying
>> it then remounting ro and fscking again (the first fsck must bring in
>> uptodate buffercache, and something is not being correctly invalidated).
>>
>> It is also not brd or minix specific -- I reproduced it with loop driver
>> and ext2 too, and probably regular disk driver will have the same problem
>> (ie. it is something in the buffercache).
>>
>> I don't know if this is the same problem as the ext3 issue -- the recipe
>> for reproducing ext3 problem includes umount, which will invalidate all
>> the buffercache unless something is holding the bdev open. But anyway I
>> am making some progress with this problem so I will try solve it first.
>>
>> I can't think of any good reason why buffercache should be going out of
>> sync here...
> 
> Ah, of course, it would be due to directory-in-pagecache. You need
> the following patch if you expect this to work.
> 
> And that confirms the ext3 problem is a different one because it
> doesn't use directory in pagecache I think. Well, I'll look at
> that one tomorrow.
> 
> Thanks,
> Nick
> 
> ---
>  fs/super.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> Index: linux-2.6/fs/super.c
> ===================================================================
> --- linux-2.6.orig/fs/super.c
> +++ linux-2.6/fs/super.c
> @@ -644,6 +644,8 @@ int do_remount_sb(struct super_block *sb
>  		acct_auto_close(sb);
>  	shrink_dcache_sb(sb);
>  	fsync_super(sb);
> +	if (flags & MS_RDONLY)
> +		invalidate_bdev(sb->s_bdev);
>  
>  	/* If we are remounting RDONLY and current sb is read/write,
>  	   make sure there are no rw files opened */
> 
> 
> 
> 

	With this applied it seems I cannot reproduce the corruption, I have to 
do more tests, but the box oopses on reboot after doing "umount -na -r".

[  193.073856] BUG: unable to handle kernel NULL pointer dereference at 
00000004
[  193.075762] IP: [<c018baa7>] invalidate_bdev+0x4/0x27
[  193.078748] *pde = 00000000
[  193.080306] Oops: 0000 [#1] SMP
[  193.082066] last sysfs file: 
/sys/devices/pci0000:00/0000:00:01.3/i2c-adapter/i2c-0/name
[  193.082066] Modules linked in: atmtcp ipt_REJECT nf_conntrack_ipv4 
nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables 
i2c_piix4 i2c_core ata_piix libata ppp_async ppp_synctty sha1_generic 
arc4 ecb ppp_mppe pppol2tp pppoatm pppoe pppox ppp_generic slhc 8021q 
garp tun softdog usbcore
[  193.082066]
[  193.082066] Pid: 1500, comm: busybox Not tainted (2.6.29-rc7 #122)
[  193.082066] EIP: 0060:[<c018baa7>] EFLAGS: 00010202 CPU: 3
[  193.082066] EIP is at invalidate_bdev+0x4/0x27
[  193.082066] EAX: 00000000 EBX: 00000001 ECX: 00000000 EDX: 00000001
[  193.082066] ESI: ce82dc00 EDI: 00000000 EBP: ce861f30 ESP: ce861f2c
[  193.082066]  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
[  193.082066] Process busybox (pid: 1500, ti=ce860000 task=ce8c0530 
task.ti=ce860000)
[  193.082066] Stack:
[  193.082066]  00000001 ce861f48 c017408a 00000001 00000001 ce861f78 
ce82dc00 ce861f64
[  193.082066]  c0184cd8 00000000 00000040 ce251000 00000001 00000040 
ce861f8c c01853d5
[  193.082066]  00000000 00000000 ce518000 cf81f140 cf401f20 00000000 
ce251000 00000000
[  193.082066] Call Trace:
[  193.082066]  [<c017408a>] ? do_remount_sb+0x4b/0xc2
[  193.082066]  [<c0184cd8>] ? do_remount+0x70/0xb5
[  193.082066]  [<c01853d5>] ? do_mount+0x107/0x181
[  193.082066]  [<c0185665>] ? sys_mount+0x6a/0xa6
[  193.082066]  [<c0102ce2>] ? syscall_call+0x7/0xb
[  193.082066] Code: 43 c0 e8 d2 74 f9 ff 58 5a 8b 45 ec 83 c0 74 e8 d8 
fb 1c 00 8b 45 e4 e8 f9 e1 fc ff 8b 45 e8 8d 65 f4 5b 5e 5f 5d c3 55 89 
e5 53 <8b> 40 04 8b 98 14 01 00 00 83 7b 60 00 74 11 e8 36 0f 00 00 83
[  193.082066] EIP: [<c018baa7>] invalidate_bdev+0x4/0x27 SS:ESP 
0068:ce861f2c
[  193.132444] ---[ end trace 47b1cfc0707471fd ]---
[  193.133287] Kernel panic - not syncing: Fatal exception
[  193.134372] Rebooting in 40 seconds.. 


-- 
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be made.
==============================================================

Re: Error testing ext3 on brd ramdisk

[Nick Piggin]

On Tue, Mar 10, 2009 at 05:49:13PM +0100, Jorge Boncompte [DTI2] wrote:
> Nick Piggin escribió:
> >Ah, of course, it would be due to directory-in-pagecache. You need
> >the following patch if you expect this to work.
> >
> >And that confirms the ext3 problem is a different one because it
> >doesn't use directory in pagecache I think. Well, I'll look at
> >that one tomorrow.
> >
> >Thanks,
> >Nick
> >
> >---
> > fs/super.c |    2 ++
> > 1 file changed, 2 insertions(+)
> >
> >Index: linux-2.6/fs/super.c
> >===================================================================
> >--- linux-2.6.orig/fs/super.c
> >+++ linux-2.6/fs/super.c
> >@@ -644,6 +644,8 @@ int do_remount_sb(struct super_block *sb
> > 		acct_auto_close(sb);
> > 	shrink_dcache_sb(sb);
> > 	fsync_super(sb);
> >+	if (flags & MS_RDONLY)
> >+		invalidate_bdev(sb->s_bdev);
> > 
> > 	/* If we are remounting RDONLY and current sb is read/write,
> > 	   make sure there are no rw files opened */
> >
> >
> >
> >
> 
> 	With this applied it seems I cannot reproduce the corruption, I have 

Ah, that sounds promising.

> 	to do more tests, but the box oopses on reboot after doing "umount -na -r".

Oh, silly me, s_bdev will be NULL for non block device based filesystems.
If you check for s_bdev != NULL there too, it should work.

> 
> [  193.073856] BUG: unable to handle kernel NULL pointer dereference at 
> 00000004
> [  193.075762] IP: [<c018baa7>] invalidate_bdev+0x4/0x27
> [  193.078748] *pde = 00000000
> [  193.080306] Oops: 0000 [#1] SMP
> [  193.082066] last sysfs file: 
> /sys/devices/pci0000:00/0000:00:01.3/i2c-adapter/i2c-0/name
> [  193.082066] Modules linked in: atmtcp ipt_REJECT nf_conntrack_ipv4 
> nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables 
> i2c_piix4 i2c_core ata_piix libata ppp_async ppp_synctty sha1_generic 
> arc4 ecb ppp_mppe pppol2tp pppoatm pppoe pppox ppp_generic slhc 8021q 
> garp tun softdog usbcore
> [  193.082066]
> [  193.082066] Pid: 1500, comm: busybox Not tainted (2.6.29-rc7 #122)
> [  193.082066] EIP: 0060:[<c018baa7>] EFLAGS: 00010202 CPU: 3
> [  193.082066] EIP is at invalidate_bdev+0x4/0x27
> [  193.082066] EAX: 00000000 EBX: 00000001 ECX: 00000000 EDX: 00000001
> [  193.082066] ESI: ce82dc00 EDI: 00000000 EBP: ce861f30 ESP: ce861f2c
> [  193.082066]  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> [  193.082066] Process busybox (pid: 1500, ti=ce860000 task=ce8c0530 
> task.ti=ce860000)
> [  193.082066] Stack:
> [  193.082066]  00000001 ce861f48 c017408a 00000001 00000001 ce861f78 
> ce82dc00 ce861f64
> [  193.082066]  c0184cd8 00000000 00000040 ce251000 00000001 00000040 
> ce861f8c c01853d5
> [  193.082066]  00000000 00000000 ce518000 cf81f140 cf401f20 00000000 
> ce251000 00000000
> [  193.082066] Call Trace:
> [  193.082066]  [<c017408a>] ? do_remount_sb+0x4b/0xc2
> [  193.082066]  [<c0184cd8>] ? do_remount+0x70/0xb5
> [  193.082066]  [<c01853d5>] ? do_mount+0x107/0x181
> [  193.082066]  [<c0185665>] ? sys_mount+0x6a/0xa6
> [  193.082066]  [<c0102ce2>] ? syscall_call+0x7/0xb
> [  193.082066] Code: 43 c0 e8 d2 74 f9 ff 58 5a 8b 45 ec 83 c0 74 e8 d8 
> fb 1c 00 8b 45 e4 e8 f9 e1 fc ff 8b 45 e8 8d 65 f4 5b 5e 5f 5d c3 55 89 
> e5 53 <8b> 40 04 8b 98 14 01 00 00 83 7b 60 00 74 11 e8 36 0f 00 00 83
> [  193.082066] EIP: [<c018baa7>] invalidate_bdev+0x4/0x27 SS:ESP 
> 0068:ce861f2c
> [  193.132444] ---[ end trace 47b1cfc0707471fd ]---
> [  193.133287] Kernel panic - not syncing: Fatal exception
> [  193.134372] Rebooting in 40 seconds.. 
> 
> 
> -- 
> ==============================================================
> Jorge Boncompte - Ingenieria y Gestion de RED
> DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
> --------------------------------------------------------------
> C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
> Tlf: +34 957 761395 / FAX: +34 957 450380
> ==============================================================
> - Sin pistachos no hay Rock & Roll...
> - Without wicker a basket cannot be made.
> ==============================================================

Re: Error testing ext3 on brd ramdisk

[Jorge Boncompte [DTI2]]

Nick Piggin escribió:
> On Tue, Mar 10, 2009 at 05:49:13PM +0100, Jorge Boncompte [DTI2] wrote:
>> Nick Piggin escribió:
>>> Ah, of course, it would be due to directory-in-pagecache. You need
>>> the following patch if you expect this to work.
>>>
>>> And that confirms the ext3 problem is a different one because it
>>> doesn't use directory in pagecache I think. Well, I'll look at
>>> that one tomorrow.
>>>
>>> Thanks,
>>> Nick
>>>
>>> ---
>>> fs/super.c |    2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> Index: linux-2.6/fs/super.c
>>> ===================================================================
>>> --- linux-2.6.orig/fs/super.c
>>> +++ linux-2.6/fs/super.c
>>> @@ -644,6 +644,8 @@ int do_remount_sb(struct super_block *sb
>>> 		acct_auto_close(sb);
>>> 	shrink_dcache_sb(sb);
>>> 	fsync_super(sb);
>>> +	if (flags & MS_RDONLY)
>>> +		invalidate_bdev(sb->s_bdev);
>>>
>>> 	/* If we are remounting RDONLY and current sb is read/write,
>>> 	   make sure there are no rw files opened */
>>>
>>>
>>>
>>>
>> 	With this applied it seems I cannot reproduce the corruption, I have 
> 
> Ah, that sounds promising.
> 
>> 	to do more tests, but the box oopses on reboot after doing "umount -na -r".
> 
> Oh, silly me, s_bdev will be NULL for non block device based filesystems.
> If you check for s_bdev != NULL there too, it should work.

	Hi Nick, no problems noticed in the last days running with the below 
patch...

--- linux-2.6.29-rc8/fs/super.c       2009-03-13 13:46:19 +0100
+++ kernel/fs/super.c       2009-03-13 13:47:50 +0100
@@ -647,6 +647,8 @@ int do_remount_sb(struct super_block *sb
                 acct_auto_close(sb);
         shrink_dcache_sb(sb);
         fsync_super(sb);
+       if (sb->s_bdev && (flags & MS_RDONLY))
+               invalidate_bdev(sb->s_bdev);

         /* If we are remounting RDONLY and current sb is read/write,
            make sure there are no rw files opened */

-- 
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be made.
==============================================================

Re: Error testing ext3 on brd ramdisk

[Denis Karpov]

[-- Attachment #1: Type: text/plain, Size: 2151 bytes --]

On Fri, Mar 13, 2009 at 06:06:07PM +0100, ext Jorge Boncompte [DTI2] wrote:
> Nick Piggin escribió:
> > On Tue, Mar 10, 2009 at 05:49:13PM +0100, Jorge Boncompte [DTI2] wrote:
> >> Nick Piggin escribió:
> >>> Ah, of course, it would be due to directory-in-pagecache. You need
> >>> the following patch if you expect this to work.
> >>>
> >>> And that confirms the ext3 problem is a different one because it
> >>> doesn't use directory in pagecache I think. Well, I'll look at
> >>> that one tomorrow.
> 	Hi Nick, no problems noticed in the last days running with the below 
> patch...
> 
> --- linux-2.6.29-rc8/fs/super.c       2009-03-13 13:46:19 +0100
> +++ kernel/fs/super.c       2009-03-13 13:47:50 +0100
> @@ -647,6 +647,8 @@ int do_remount_sb(struct super_block *sb
>                  acct_auto_close(sb);
>          shrink_dcache_sb(sb);
>          fsync_super(sb);
> +       if (sb->s_bdev && (flags & MS_RDONLY))
> +               invalidate_bdev(sb->s_bdev);
> 
>          /* If we are remounting RDONLY and current sb is read/write,
>             make sure there are no rw files opened */
> 

Hello, 

first off, sorry if you getting this email twice.

I also tried to do ext3/ext4 fs smoketesting and used Adraian's
script.  I am consistently getting the same results - filesystem get's
corrupted. 
I tested on quad Xeon, with patches posted in this thread.

1. tests with brd:
- ext3fs on brd
    corruption (see attached ext3fs.brd.corruption.txt)
- ext4fs on brd
    corruption (see attached ext4fs.brd.corruption.txt)

In both cases I saw some complains from JBD/JBD2:
 JBD: Detected IO errors while flushing file data on

2. I enabled JBD debugging, re-run the tests. Console was 
flooded with messages and in the end I got a soft lockup.
I cannot consistently reproduce this (see attached 
brd.ext3fs.softlock.txt).

Just to be sure I re-run the tests on real block device (usb stick)

3. tests with real block device (usb stick)
- ext3fs
    no fs currption (overnight run)
- ext4fs 
    no fs currption (overnight run)

Any ideas what else can be done here? I'd like to find out if this is
filesystem or brd related fault.

Denis

[-- Attachment #2: brd.ext3fs.corruption.txt --]
[-- Type: text/plain, Size: 973 bytes --]

...
-------------------------------------------------------------
Cycle 15
Fri Mar 13 11:01:22 EDT 2009
Mounting
Removing old fsstress data
Starting fsstress
Sleeping 30 seconds
seed = 1237275074
Stopping fsstress
 8572 pts/0    00:00:00 fsstress_ext3
 8575 pts/0    00:00:25 fsstress_ext3
 8576 pts/0    00:00:25 fsstress_ext3
 8577 pts/0    00:00:25 fsstress_ext3
./brd_test_ext3.sh: line 37:  8572 Terminated              `pwd`/fsstress_ext3 -d $TESTDIR/work -p 3 -l 0 -n 100000000
Unmounting
Checking
/dev/ram0: HTREE directory inode 94 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram0: HTREE directory inode 218 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram0: HTREE directory inode 813 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram0: Entry 'cd8f' in /work/p1/d2f/d13df/d18e3/d521/d14f7 (218) has an incorrect filetype (was 3, should be 1).


/dev/ram0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)


[-- Attachment #3: brd.ext3fs.softlock.txt --]
[-- Type: text/plain, Size: 26468 bytes --]

...
JBD: Detected IO errors while flushing file data on 
ram0                       
...

and then relatively soon (cycle 11) final failure:

...
/dev/ram0: UNEXPECTED INCONSISTENCY; RUN fsck 
MANUALLY.                        
...


[  137.287143] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287153] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 4
[  137.287165] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345848, comm8
[  137.287185] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  137.287191] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  137.287196] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com8
[  137.287208] (fs/jbd/journal.c, 548): log_wait_commit: JBD: want 345849, j_co8
[  137.287215] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[  137.287220] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345848, comm9
[  137.287223] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[  137.287227] (fs/jbd/journal.c, 548): log_wait_commit: <7>(fs/jbd/commit.c, 39
 3458 ttyS0    0[  137.287237] JBD: want 345849, j_commit_sequence=345848       
0:00:00 fsstress[  137.287249] (fs/jbd/revoke.c, 521): journal_write_revoke_recs
                                                                                
 3460 ttyS0   [  137.287263] (fs/jbd/checkpoint.c, 753): __journal_drop_transace
 00:00:21 fsstre[  137.287267] (fs/jbd/commit.c, 955): journal_commit_transacti4
ss                                                                              
 3461 ttyS0 [  137.287278] (fs/jbd/journal.c, 143): kjournald: commit_sequence=9
   00:00:20 fsst[  137.287298] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloC
ress <defunct>                                                                  
[  137.287302] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com9
 3462 ttyS0    0[  137.287311] (fs/jbd/journal.c, 548): log_wait_commit: JBD: w9
0:00:00 fsstress[  137.287318] (fs/jbd/journal.c, 191): kjournald: kjournald was
                                                                                
[  137.287323] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345849, comm0
[  137.287326] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[  137.287329] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin0
[  137.287340] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[  137.287355] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287359] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 4
[  137.287367] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345850, comm0
[  137.287386] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  137.287390] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com0
[  137.287401] (fs/jbd/journal.c, 548): log_wait_commit: JBD: want 345851, j_co0

[  137.287408] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[  137.287413] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345850, comm1
[  137.287416] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[  137.287419] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin1
[  137.287430] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287435] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287443] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287448] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287457] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[  137.287470] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287474] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 4
[  137.287482] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345851, comm1[  137.287718] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  137.287722] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com1
[  137.287733] (fs/jbd/journal.c, 548): log_wait_commit: JBD: want 345852, j_co1
[  137.287741] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[  137.287746] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345851, comm2
[  137.287751] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[  137.287754] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin2
[  137.287762] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287768] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287774] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287781] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287786] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge[  137.287791] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287795] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.287804] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[  137.287857] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 4
[  137.287871] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345852, comm2
[  137.287938] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  137.287942] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com2
[  137.287951] (fs/jbd/journal.c, 548): log_wait_commit: JBD: want 345853, j_co2
[  137.287959] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[  137.287963] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345852, comm3
[  137.287968] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[  137.287971] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin3
[  137.287981] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[  137.288020] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.288026] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 4
[  137.288035] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345853, comm3
[  137.288099] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  137.288103] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com3
[  137.288112] (fs/jbd/journal.c, 548): log_wait_commit: JBD: want 345854, j_co3
[  137.288120] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[  137.288125] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345853, comm4
[  137.288128] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          [  137.288131] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin4
[  137.288142] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[  137.288184] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.288190] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 4
[  137.288199] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345854, comm4
[  137.288264] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  137.288268] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com4
[  137.288282] (fs/jbd/journal.c, 548): log_wait_commit: JBD: want 345855, j_co4
[  137.288290] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[  137.288295] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345854, comm5
[  137.288299] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[  137.288302] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin5
[  137.288312] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[  137.288352] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  137.288358] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 4
[  137.288367] (fs/jbd/journal.c, 143): kjournald: commit_sequence=345855, comm5
[  148.971458] JBD: Detected IO errors while flushing file data on ram1         
[  148.972649] JBD: Detected IO errors while flushing file data on ram1         
[  148.975145] JBD: Detected IO errors while flushing file data on ram1         
[  150.036402] JBD: Detected IO errors while flushing file data on ram1         
[ 1681.129521] Clocksource tsc unstable (delta = 1546657291253 ns)              
[ 1681.130181] BUG: soft lockup - CPU#2 stuck for 1414s! [fsstress:3462]        
[ 1681.130181] Modules linked in: brd ext3 jbd                                  
[ 1681.130181] irq event stamp: 37867                                           
[ 1681.130181] hardirqs last  enabled at (37866): [<b042af82>] _spin_unlock_irq0
[ 1681.130181] hardirqs last disabled at (37867): [<b0103ada>] apic_timer_inter4
[ 1681.130181] softirqs last  enabled at (37522): [<b012ff92>] __do_softirq+0x10
[ 1681.130181] softirqs last disabled at (37833): [<b013004d>] do_softirq+0x6d/0
[ 1681.130181]                                                                  
[ 1681.130181] Pid: 3462, comm: fsstress Not tainted (2.6.29-rc7-00102-g7a203f3 
[ 1681.130181] EIP: 0060:[<b042af85>] EFLAGS: 00000202 CPU: 2                   
[ 1681.130181] EIP is at _spin_unlock_irq+0x25/0x50                             
[ 1681.130181] EAX: edfe7b8c EBX: ef880000 ECX: 00000004 EDX: efa003d0          
[ 1681.130181] ESI: ef880000 EDI: 00000102 EBP: edfe7b90 ESP: edfe7b8c          
[ 1681.130181]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068                    
[ 1681.130181] CR0: 8005003b CR2: a7ebf0f0 CR3: 3c434000 CR4: 000006d0          
[ 1681.130181] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000          




[  839.603442] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin6
[  839.603458] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[  839.603481] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  839.603488] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 9
[  839.603495] (fs/jbd/journal.c, 143): kjournald: commit_sequence=1490376, com6
[  839.603521] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  839.603528] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com6
[  839.603541] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[  839.603545] (fs/jbd/journal.c, 143): kjournald: commit_sequence=1490376, com7
[  839.603551] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[  839.603556] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin7
[  839.603569] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[  839.603591] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[  839.603597] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 9
[  839.603606] (fs/jbd/journal.c, 143): kjournald: commit_sequence=1490377, com7
[  839.603636] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  839.603643] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com7
[  839.603655] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[  839.603660] (fs/jbd/journal.c, 143): kjournald: commit_sequence=1490377, com8
[  839.603664] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[  839.603670] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin8
[  839.603683] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[  839.603708] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge[  839.603715] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 9
[  839.603723] (fs/jbd/journal.c, 143): kjournald: commit_sequence=1490378, com8
[  839.603757] (fs/ext3/balloc.c, 1449): ext3_should_retry_alloc: ram1: retryinC
[  839.603763] (fs/jbd/journal.c, 446): __log_start_commit: JBD: requesting com8
[  839.603777] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[  839.603782] (fs/jbd/journal.c, 143): kjournald: commit_sequence=1490378, com9
[  839.603788] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[  839.603794] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin9
 4401 ttyS0    0[  839.603813] (fs/jbd/revoke.c, 521): journal_write_revoke_recs
0:00:24 fsstress[  839.603837] (fs/jbd/checkpoint.c, 753): __journal_drop_transe
 <defunct>                                                                      
 440[  839.603844] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: com9
2 ttyS0    00:00[  839.603850] (fs/jbd/journal.c, 143): kjournald: commit_seque9
[ 1833.097021] Clocksource tsc unstable (delta = 993639928371 ns)               
[ 1833.099443] (fs/jbd/journal.c, 191): kjournald: kjournald wakes              
[ 1833.099448] (fs/jbd/journal.c, 199): kjournald: woke because of timeout      
[ 1833.099451] (fs/jbd/journal.c, 143): kjournald: commit_sequence=1490379, com0
[ 1833.099456] (fs/jbd/journal.c, 146): kjournald: OK, requests differ          
[ 1833.099463] (fs/jbd/commit.c, 345): journal_commit_transaction: JBD: startin0
[ 1833.099479] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge[ 1833.099488] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[ 1833.099501] (fs/jbd/revoke.c, 521): journal_write_revoke_records: Wrote 0 res
[ 1833.099542] (fs/jbd/checkpoint.c, 753): __journal_drop_transaction: Droppinge
[ 1833.099547] (fs/jbd/commit.c, 955): journal_commit_transaction: JBD: commit 9
[ 1833.099554] (fs/jbd/journal.c, 143): kjournald: commit_sequence=1490380, com0
[ 1833.099631] BUG: soft lockup - CPU#3 stuck for 921s! [fsstress:4402]         
[ 1833.099631] Modules linked in: brd ext3 jbd                                  
[ 1833.099631] irq event stamp: 5787241                                         
[ 1833.099631] hardirqs last  enabled at (5787240): [<b042af82>] _spin_unlock_i0
[ 1833.099631] hardirqs last disabled at (5787241): [<b0103ada>] apic_timer_int4
[ 1833.099631] softirqs last  enabled at (5787190): [<b012ff92>] __do_softirq+00
[ 1833.099631] softirqs last disabled at (5787221): [<b013004d>] do_softirq+0x60
[ 1833.099631]                                                                  
[ 1833.099631] Pid: 4402, comm: fsstress Not tainted (2.6.29-rc7-00102-g7a203f3 
[ 1833.099631] EIP: 0060:[<b042af85>] EFLAGS: 00000202 CPU: 3                   
[ 1833.099631] EIP is at _spin_unlock_irq+0x25/0x50                             [ 1833.099631] EAX: dce59ce4 EBX: ef88e000 ECX: 00000004 EDX: eed3ed70          
[ 1833.099631] ESI: ef88e000 EDI: 00000102 EBP: dce59ce8 ESP: dce59ce4          
[ 1833.099631]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068                    
[ 1833.099631] CR0: 8005003b CR2: af868fdc CR3: 3e7e6000 CR4: 000006d0          
[ 1833.099631] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000          
[ 1833.099631] DR6: ffff0ff0 DR7: 00000400                                      
[ 1833.099631] Call Trace:                                                      
[ 1833.099631]  [<b0133ea6>] run_timer_softirq+0x146/0x1c0                      
[ 1833.099631]  [<b014ec71>] ? mark_held_locks+0x41/0x80                        
[ 1833.099631]  [<b013bd70>] ? delayed_work_timer_fn+0x0/0x30                   
[ 1833.099631]  [<b012ff0f>] __do_softirq+0x9f/0x170                            
[ 1833.099631]  [<b013004d>] do_softirq+0x6d/0x80                               
[ 1833.099631]  [<b013029d>] irq_exit+0x7d/0xa0                                 
[ 1833.099631]  [<b0114fee>] smp_apic_timer_interrupt+0x5e/0x90                 
[ 1833.099631]  [<b0264828>] ? trace_hardirqs_off_thunk+0xc/0x14                
[ 1833.099631]  [<b0103ae1>] apic_timer_interrupt+0x2d/0x34                     
[ 1833.099631]  [<b042afdf>] ? _spin_unlock_irqrestore+0x2f/0x70                
[ 1833.099631]  [<b012b7dd>] ? vprintk+0x29d/0x3d0                              
[ 1833.099631]  [<f0a39fd9>] ? journal_stop+0x169/0x3a0 [jbd]                   [ 1833.099631]  [<b0427b13>] printk+0x18/0x1a                                   
[ 1833.099631]  [<f0a76cb0>] ext3_should_retry_alloc+0x80/0xa0 [ext3]           
[ 1833.099631]  [<f0a81396>] ext3_create+0x46/0x100 [ext3]                      
[ 1833.099631]  [<b0198c7c>] vfs_create+0xbc/0x120                              
[ 1833.099631]  [<b042b03d>] ? _spin_unlock+0x1d/0x40                           
[ 1833.099631]  [<f0a81350>] ? ext3_create+0x0/0x100 [ext3]                     
[ 1833.099631]  [<b019be80>] do_filp_open+0x6d0/0x7e0                           
[ 1833.099631]  [<b042b03d>] ? _spin_unlock+0x1d/0x40                           
[ 1833.099631]  [<b01a5148>] ? alloc_fd+0xe8/0x100                              
[ 1833.099631]  [<b018e2e9>] do_sys_open+0x59/0xf0                              
[ 1833.099631]  [<b018e3e9>] sys_open+0x29/0x40                                 
[ 1833.099631]  [<b018e420>] sys_creat+0x20/0x30                                
[ 1833.099631]  [<b0103385>] sysenter_do_call+0x12/0x35                         
[ 1833.099631] Kernel panic - not syncing: softlockup: hung tasks               
[ 1833.099631] ------------[ cut here ]------------                             [ 1833.099631] WARNING: at kernel/mutex.c:351 mutex_trylock+0x13f/0x1a0()       
[ 1833.099631] Hardware name: Precision WorkStation 650                         
[ 1833.099631] Modules linked in: brd ext3 jbd                                  
[ 1833.099631] Pid: 4402, comm: fsstress Not tainted 2.6.29-rc7-00102-g7a203f3 4
[ 1833.099631] Call Trace:                                                      
[ 1833.099631]  [<b0427b13>] ? printk+0x18/0x1a                                 
[ 1833.099631]  [<b012aa33>] warn_slowpath+0x73/0xd0                            
[ 1833.099631]  [<b014ded5>] ? check_usage_forwards+0x45/0xb0                   
[ 1833.099631]  [<b014d24a>] ? save_trace+0x3a/0xa0                             
[ 1833.099631]  [<b014e4ed>] ? mark_lock+0x4fd/0xc40                            
[ 1833.099631]  [<b014f9d7>] ? __lock_acquire+0x147/0x18f0                      
[ 1833.099631]  [<b0145195>] ? sched_clock_cpu+0x135/0x190                      
[ 1833.099631]  [<b042904f>] mutex_trylock+0x13f/0x1a0                          
[ 1833.099631]  [<b015c50b>] crash_kexec+0x1b/0xc0                              
[ 1833.099631]  [<b014d3ab>] ? trace_hardirqs_off+0xb/0x10                      
[ 1833.099631]  [<b042b00d>] ? _spin_unlock_irqrestore+0x5d/0x70                
[ 1833.099631]  [<b0143f0a>] ? down_trylock+0x2a/0x40                           
[ 1833.099631]  [<b012b4a7>] ? console_unblank+0x17/0x80                        
[ 1833.099631]  [<b0427a52>] panic+0x57/0x100                                   
[ 1833.099631]  [<b016233d>] softlockup_tick+0x15d/0x190                        [ 1833.099631]  [<b0134277>] run_local_timers+0x17/0x20                         
[ 1833.099631]  [<b01342af>] update_process_times+0x2f/0x70                     
[ 1833.099631]  [<b014b13d>] tick_sched_timer+0x5d/0xc0                         
[ 1833.099631]  [<b014b0e0>] ? tick_sched_timer+0x0/0xc0                        
[ 1833.099631]  [<b01427b2>] __run_hrtimer+0x42/0x100                           
[ 1833.099631]  [<b042b1b5>] ? _spin_lock+0x45/0x50                             
[ 1833.099631]  [<b0143535>] hrtimer_interrupt+0x175/0x220                      
[ 1833.099631]  [<b0114fe9>] smp_apic_timer_interrupt+0x59/0x90                 
[ 1833.099631]  [<b0264828>] ? trace_hardirqs_off_thunk+0xc/0x14                
[ 1833.099631]  [<b0103ae1>] apic_timer_interrupt+0x2d/0x34                     
[ 1833.099631]  [<b042af85>] ? _spin_unlock_irq+0x25/0x50                       
[ 1833.099631]  [<b0133ea6>] run_timer_softirq+0x146/0x1c0                      
[ 1833.099631]  [<b014ec71>] ? mark_held_locks+0x41/0x80                        
[ 1833.099631]  [<b013bd70>] ? delayed_work_timer_fn+0x0/0x30                   
[ 1833.099631]  [<b012ff0f>] __do_softirq+0x9f/0x170                            
[ 1833.099631]  [<b013004d>] do_softirq+0x6d/0x80                               
[ 1833.099631]  [<b013029d>] irq_exit+0x7d/0xa0                                 
[ 1833.099631]  [<b0114fee>] smp_apic_timer_interrupt+0x5e/0x90                 
[ 1833.099631]  [<b0264828>] ? trace_hardirqs_off_thunk+0xc/0x14                
[ 1833.099631]  [<b0103ae1>] apic_timer_interrupt+0x2d/0x34                     [ 1833.099631]  [<b042afdf>] ? _spin_unlock_irqrestore+0x2f/0x70                
[ 1833.099631]  [<b012b7dd>] ? vprintk+0x29d/0x3d0                              
[ 1833.099631]  [<f0a39fd9>] ? journal_stop+0x169/0x3a0 [jbd]                   
[ 1833.099631]  [<b0427b13>] printk+0x18/0x1a                                   
[ 1833.099631]  [<f0a76cb0>] ext3_should_retry_alloc+0x80/0xa0 [ext3]           
[ 1833.099631]  [<f0a81396>] ext3_create+0x46/0x100 [ext3]                      
[ 1833.099631]  [<b0198c7c>] vfs_create+0xbc/0x120                              
[ 1833.099631]  [<b042b03d>] ? _spin_unlock+0x1d/0x40                           
[ 1833.099631]  [<f0a81350>] ? ext3_create+0x0/0x100 [ext3]                     
[ 1833.099631]  [<b019be80>] do_filp_open+0x6d0/0x7e0                           
[ 1833.099631]  [<b042b03d>] ? _spin_unlock+0x1d/0x40                           
[ 1833.099631]  [<b01a5148>] ? alloc_fd+0xe8/0x100                              
[ 1833.099631]  [<b018e2e9>] do_sys_open+0x59/0xf0                              
[ 1833.099631]  [<b018e3e9>] sys_open+0x29/0x40                                 
[ 1833.099631]  [<b018e420>] sys_creat+0x20/0x30                                [ 1833.099631]  [<b0103385>] sysenter_do_call+0x12/0x35                         
[ 1833.099631] ---[ end trace 1b613fe912a9ef3d ]---                             
[ 1833.099631] ------------[ cut here ]------------                             
[ 1833.099631] WARNING: at kernel/smp.c:329 smp_call_function_many+0x1d2/0x230()
[ 1833.099631] Hardware name: Precision WorkStation 650                         
[ 1833.099631] Modules linked in: brd ext3 jbd                                  
[ 1833.099631] Pid: 4402, comm: fsstress Tainted: G        W  2.6.29-rc7-00102-4
[ 1833.099631] Call Trace:                                                      
[ 1833.099631]  [<b0427b13>] ? printk+0x18/0x1a                                 
[ 1833.099631]  [<b012aa33>] warn_slowpath+0x73/0xd0                            
[ 1833.099631]  [<b014f9d7>] ? __lock_acquire+0x147/0x18f0                      
[ 1833.099631]  [<b0145195>] ? sched_clock_cpu+0x135/0x190                      
[ 1833.099631]  [<b014d3ab>] ? trace_hardirqs_off+0xb/0x10                      
[ 1833.099631]  [<b0428e6e>] ? __mutex_unlock_slowpath+0xce/0x160               
[ 1833.099631]  [<b0428fc3>] ? mutex_trylock+0xb3/0x1a0                         
[ 1833.099631]  [<b0428f08>] ? mutex_unlock+0x8/0x10                            
[ 1833.099631]  [<b0155b22>] smp_call_function_many+0x1d2/0x230                 
[ 1833.099631]  [<b0109cf0>] ? stop_this_cpu+0x0/0x40                           
[ 1833.099631]  [<b0155bad>] smp_call_function+0x2d/0x60                        
[ 1833.099631]  [<b011399e>] native_smp_send_stop+0x1e/0x60                     [ 1833.099631]  [<b0427a58>] panic+0x5d/0x100                                   
[ 1833.099631]  [<b016233d>] softlockup_tick+0x15d/0x190                        
[ 1833.099631]  [<b0134277>] run_local_timers+0x17/0x20                         
[ 1833.099631]  [<b01342af>] update_process_times+0x2f/0x70                     
[ 1833.099631]  [<b014b13d>] tick_sched_timer+0x5d/0xc0                         
[ 1833.099631]  [<b014b0e0>] ? tick_sched_timer+0x0/0xc0                        
[ 1833.099631]  [<b01427b2>] __run_hrtimer+0x42/0x100                           
[ 1833.099631]  [<b042b1b5>] ? _spin_lock+0x45/0x50                             
[ 1833.099631]  [<b0143535>] hrtimer_interrupt+0x175/0x220                      
[ 1833.099631]  [<b0114fe9>] smp_apic_timer_interrupt+0x59/0x90                 
[ 1833.099631]  [<b0264828>] ? trace_hardirqs_off_thunk+0xc/0x14                
[ 1833.099631]  [<b0103ae1>] apic_timer_interrupt+0x2d/0x34                     
[ 1833.099631]  [<b042af85>] ? _spin_unlock_irq+0x25/0x50                       
[ 1833.099631]  [<b0133ea6>] run_timer_softirq+0x146/0x1c0                      
[ 1833.099631]  [<b014ec71>] ? mark_held_locks+0x41/0x80                        [ 1833.099631]  [<b013bd70>] ? delayed_work_timer_fn+0x0/0x30                   
[ 1833.099631]  [<b012ff0f>] __do_softirq+0x9f/0x170                            
[ 1833.099631]  [<b013004d>] do_softirq+0x6d/0x80                               
[ 1833.099631]  [<b013029d>] irq_exit+0x7d/0xa0                                 
[ 1833.099631]  [<b0114fee>] smp_apic_timer_interrupt+0x5e/0x90                 
[ 1833.099631]  [<b0264828>] ? trace_hardirqs_off_thunk+0xc/0x14                
[ 1833.099631]  [<b0103ae1>] apic_timer_interrupt+0x2d/0x34                     
[ 1833.099631]  [<b042afdf>] ? _spin_unlock_irqrestore+0x2f/0x70                
[ 1833.099631]  [<b012b7dd>] ? vprintk+0x29d/0x3d0                              
[ 1833.099631]  [<f0a39fd9>] ? journal_stop+0x169/0x3a0 [jbd]                   
[ 1833.099631]  [<b0427b13>] printk+0x18/0x1a                                   
[ 1833.099631]  [<f0a76cb0>] ext3_should_retry_alloc+0x80/0xa0 [ext3]           
[ 1833.099631]  [<f0a81396>] ext3_create+0x46/0x100 [ext3]                      
[ 1833.099631]  [<b0198c7c>] vfs_create+0xbc/0x120                              
[ 1833.099631]  [<b042b03d>] ? _spin_unlock+0x1d/0x40                           
[ 1833.099631]  [<f0a81350>] ? ext3_create+0x0/0x100 [ext3]                     
[ 1833.099631]  [<b019be80>] do_filp_open+0x6d0/0x7e0                           
[ 1833.099631]  [<b042b03d>] ? _spin_unlock+0x1d/0x40                           
[ 1833.099631]  [<b01a5148>] ? alloc_fd+0xe8/0x100                              
[ 1833.099631]  [<b018e2e9>] do_sys_open+0x59/0xf0                              [ 1833.099631]  [<b018e3e9>] sys_open+0x29/0x40                                 
[ 1833.099631]  [<b018e420>] sys_creat+0x20/0x30                                
[ 1833.099631]  [<b0103385>] sysenter_do_call+0x12/0x35                         
[ 1833.099631] ---[ end trace 1b613fe912a9ef3e ]---                             

[-- Attachment #4: brd.ext4fs.corruption.txt --]
[-- Type: text/plain, Size: 872 bytes --]

-------------------------------------------------------------
Cycle 12
Fri Mar 13 10:59:33 EDT 2009
Mounting
Removing old fsstress data
Starting fsstress
Sleeping 30 seconds
seed = 1237202926
Stopping fsstress
 8461 pts/1    00:00:00 fsstress_ext4
 8464 pts/1    00:00:19 fsstress_ext4
 8465 pts/1    00:00:19 fsstress_ext4
 8466 pts/1    00:00:19 fsstress_ext4
./brd_test_ext4.sh: line 36:  8461 Terminated              `pwd`/fsstress_ext4 -d $TESTDIR/work -p 3 -l 0 -n 100000000
Unmounting
Checking
/dev/ram1: HTREE directory inode 352 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram1: HTREE directory inode 713 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram1: Entry 'c2d8' in /work/p0/da/d124/d544 (713) has an incorrect filetype (was 3, should be 1).


/dev/ram1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)

Re: Error testing ext3 on brd ramdisk

[Nick Piggin]

On Tue, Mar 17, 2009 at 11:40:19AM +0200, Denis Karpov wrote:
> Hello, 
> 
> first off, sorry if you getting this email twice.

No problem, I'm not exactly able to reproduce it myself, but Jan Kara
has just fixed some issues which could explain it: they happen under
memory pressure so I may not have triggered it if I didn't put it
under pressure.

Jan's fixes are here:

http://marc.info/?l=linux-ext4&m=123731584711382&w=2

It would be interesting to try them, and if they don't work maybe
he's also interested so I cc'ed him.

 
> I also tried to do ext3/ext4 fs smoketesting and used Adraian's
> script.  I am consistently getting the same results - filesystem get's
> corrupted. 
> I tested on quad Xeon, with patches posted in this thread.
> 
> 1. tests with brd:
> - ext3fs on brd
>     corruption (see attached ext3fs.brd.corruption.txt)
> - ext4fs on brd
>     corruption (see attached ext4fs.brd.corruption.txt)
> 
> In both cases I saw some complains from JBD/JBD2:
>  JBD: Detected IO errors while flushing file data on
> 
> 2. I enabled JBD debugging, re-run the tests. Console was 
> flooded with messages and in the end I got a soft lockup.
> I cannot consistently reproduce this (see attached 
> brd.ext3fs.softlock.txt).
> 
> Just to be sure I re-run the tests on real block device (usb stick)
> 
> 3. tests with real block device (usb stick)
> - ext3fs
>     no fs currption (overnight run)
> - ext4fs 
>     no fs currption (overnight run)

It's possible the real block device is not fast enough to trigger
it, or different timings don't trigger it (brd requests complete
immediately wheras real devices tend to complete afterwards,
from (soft)interrupt context). 

Or it could be that brd is consuming some more memory to push
the system into reclaim and exposing those bugs Jan has fixed...


> Any ideas what else can be done here? I'd like to find out if this is
> filesystem or brd related fault.

Yes, thanks for persisting. If you can test the patches and see
if they help? If not, does ext2 show corruption? How about ext3
on loop device (with backing file from tmpfs/ramfs for speed).

Thanks,
Nick

Re: Error testing ext3 on brd ramdisk

[Jan Kara]

> On Tue, Mar 17, 2009 at 11:40:19AM +0200, Denis Karpov wrote:
> > Hello, 
> > 
> > first off, sorry if you getting this email twice.
> 
> No problem, I'm not exactly able to reproduce it myself, but Jan Kara
> has just fixed some issues which could explain it: they happen under
> memory pressure so I may not have triggered it if I didn't put it
> under pressure.
> 
> Jan's fixes are here:
> 
> http://marc.info/?l=linux-ext4&m=123731584711382&w=2
> 
> It would be interesting to try them, and if they don't work maybe
> he's also interested so I cc'ed him.
> 
>  
> > I also tried to do ext3/ext4 fs smoketesting and used Adraian's
> > script.  I am consistently getting the same results - filesystem get's
> > corrupted. 
> > I tested on quad Xeon, with patches posted in this thread.
> > 
> > 1. tests with brd:
> > - ext3fs on brd
> >     corruption (see attached ext3fs.brd.corruption.txt)
> > - ext4fs on brd
> >     corruption (see attached ext4fs.brd.corruption.txt)
> > 
> > In both cases I saw some complains from JBD/JBD2:
> >  JBD: Detected IO errors while flushing file data on
  Yes, my patches fix exactly this problem. So please try running with
them. I'm not sure about that HTREE corruption you see during fsck. That
seems to be a separate issue.

> > 2. I enabled JBD debugging, re-run the tests. Console was 
> > flooded with messages and in the end I got a soft lockup.
> > I cannot consistently reproduce this (see attached 
> > brd.ext3fs.softlock.txt).
  Yes, this usually produces far too many messages. The soft lockup was
probably caused by the machine being too busy logging all the messages
(log files are synced which adds much more to the load of the
filesystem). I'd probably leave that aside for now and concentrate on
the corruption problem.

								Honza
-- 
Jan Kara <jack@suse.cz>
SuSE CR Labs

Re: Error testing ext3 on brd ramdisk

[Denis Karpov]

[-- Attachment #1: Type: text/plain, Size: 729 bytes --]

> > Jan's fixes are here:
> > http://marc.info/?l=linux-ext4&m=123731584711382&w=2
> > It would be interesting to try them, and if they don't work maybe
> > he's also interested so I cc'ed him.

Hi, 

thank you reppl. I re-run the tests with this patch.

> > > 
> > > In both cases I saw some complains from JBD/JBD2:
> > >  JBD: Detected IO errors while flushing file data on
>   Yes, my patches fix exactly this problem. So please try running with
> them. I'm not sure about that HTREE corruption you see during fsck. That
> seems to be a separate issue.
Unfortunately it looks like the problem is not fixed - JBD still complains
and in the end HTREE is getting damaged, in both ext3 and ext4 tests (see
attached logs).

Denis

[-- Attachment #2: ext3.htree.txt --]
[-- Type: text/plain, Size: 6376 bytes --]

-------------------------------------------------------------                   
Cycle 34                                                                        
Fri Mar 20 08:06:06 EDT 2009                                                    
Mounting                                                                        
[ 1128.228621] EXT3 FS on ram0, internal journal                                
[ 1128.232046] kjournald starting.  Commit interval 5 seconds                   
[ 1128.238557] EXT3-fs: mounted filesystem with ordered data mode.              
Removing old fsstress data                                                      
Starting fsstress                                                               
Sleeping 30 seconds                                                             
seed = 1238324876                                                               
[ 1139.101289] JBD: Detected IO errors while flushing file data on ram0         
[ 1139.116050] JBD: Detected IO errors while flushing file data on ram0         
[ 1139.124125] JBD: Detected IO errors while flushing file data on ram0         
[ 1140.100787] JBD: Detected IO errors while flushing file data on ram0         
[ 1140.375989] JBD: Detected IO errors while flushing file data on ram0         
[ 1141.313458] JBD: Detected IO errors while flushing file data on ram0         
[ 1142.387028] JBD: Detected IO errors while flushing file data on ram0         
[ 1142.668047] JBD: Detected IO errors while flushing file data on ram0         [ 1143.035936] JBD: Detected IO errors while flushing file data on ram0         
[ 1143.160422] JBD: Detected IO errors while flushing file data on ram0         
Stopping fsstress                                                               
 3974 ttyS0    00:00:00 fsstress_ext3                                           
 3977 ttyS0    00:00:20 fsstress_ext3                                           
 3978 ttyS0    00:00:20 fsstress_ext3                                           
 3979 ttyS0    00:00:20 fsstress_ext3                                           
./brd_test_ext3.sh: line 37:  3974 Terminated              `pwd`/fsstress_ext3 -
d $TESTDIR/work -p 3 -l 0 -n 100000000                                          
Unmounting                                                                      
Checking                                                                        
/dev/ram0: HTREE directory inode 42 has an invalid root node.                   HTREE INDEX CLEARED.                                                            
/dev/ram0: Entry 'c302b' in /work/p1/da (42) has an incorrect filetype (was 3, s
hould be 1).                                                                    
                                                                                
                                                                                
/dev/ram0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.                         
        (i.e., without -a or -p options)                                        

3# fsck /dev/ram0                                      
fsck 1.41.3 (12-Oct-2008)                                                       
e2fsck 1.41.3 (12-Oct-2008)                                                     
/dev/ram0 contains a file system with errors, check forced.                     
Pass 1: Checking inodes, blocks, and sizes                                      
Pass 2: Checking directory structure                                            
Entry 'c302b' in /work/p1/da (42) has an incorrect filetype (was 3, should be 1)
.                                                                               
Fix<y>? yes                                                                     
                                                                                
Entry 'd3699' in /work/p1/da (42) is a link to directory /work/p1/da/d18a/d3874/
d278f/d2401/d3e6a/d4380/d33e8/d2a30/d3ad4/d45f3 (968).                          
Clear<y>? yes                                                                   
                                                                                
Entry 'd3ad4' in /work/p1/da/d18a/d3874/d278f/d2401/d3e6a/d4380/d33e8/d2a30 (192
) is a link to directory /work/p1/da/d207a (811).                               Clear<y>? yes                                                                   
                                                                                
Entry 'd18a' in /work/p1/da (42) is a link to directory /work/p1/da/d18a (491). 
Clear<y>? yes                                                                   
                                                                                
Pass 3: Checking directory connectivity                                         
'..' in /work/p1/da/d207a (811) is /work/p1/da/d18a/d3874/d278f/d2401/d3e6a/d438
0/d33e8/d2a30 (192), should be /work/p1/da (42).                                
Fix<y>? yes                                                                     
                                                                                
Pass 4: Checking reference counts                                               
Inode 53 ref count is 1, should be 2.  Fix<y>? yes                                                                                                              
Inode 67 ref count is 1, should be 2.  Fix<y>? yes                              
                                                                                
Inode 86 ref count is 3, should be 4.  Fix<y>? yes                              
                                                                                
...

Inode 945 ref count is 1, should be 2.  Fix<y>? yes                             
                                                                                
Inode 993 ref count is 7, should be 8.  Fix<y>? yes                             
                                                                                
Pass 5: Checking group summary information                                      
                                                                                
/dev/ram0: ***** FILE SYSTEM WAS MODIFIED *****                                 /dev/ram0: 1024/1024 files (18.4% non-contiguous), 4094/4096 blocks             


[-- Attachment #3: ext4.htree.txt --]
[-- Type: text/plain, Size: 6457 bytes --]

-------------------------------------------------------------                   
Cycle 9                                                                         
Fri Mar 20 08:18:28 EDT 2009                                                    
Mounting                                                                        
[ 1870.516310] EXT4-fs: barriers enabled                                        
[ 1870.520359] kjournald2 starting: pid 5729, dev ram1:8, commit interval 5 seco
nds                                                                             
Removing old fss[ 1870.520396] EXT4 FS on ram1, internal journal on ram1:8      
tress data                                                                      
[ 1870.520399] EXT4-fs: delayed allocation enabled                              
[ 1870.520401] EXT4-fs: file extents enabled                                    
[ 1870.520553] EXT4-fs: mballoc enabled                                         
[ 1870.520556] EXT4-fs: mounted filesystem ram1 with ordered data mode          
[ 1870.570047] JBD: barrier-based sync failed on ram1:8 - disabling barriers    
Starting fsstress                                                               
Sleeping 30 seconds                                                             
seed = 1237467072                                                               
Stopping fsstress                                                                5732 ttyS0    00:00:00 fsstress_ext4                                           
 5735 ttyS0    00:00:28 fsstress_ext4                                           
 5736 ttyS0    00:00:28 fsstress_ext4                                           
 5737 ttyS0    00:00:28 fsstress_ext4                                           
./brd_test_ext4.sh: line 36:  5732 Terminated              `pwd`/fsstress_ext4 -
d $TESTDIR/work -p 3 -l 0 -n 100000000                                          
Unmounting                                                                      
[ 1901.751383] EXT4-fs: mballoc: 7905 blocks 4022 reqs (13 success)             
[ 1901.757443] EXT4-fs: mballoc: 8495 extents scanned, 341 goal hits, 6 2^N hits
, 4 breaks, 38 lost                                                             
[ 1901.766253] EXT4-fs: mballoc: 1 generated and it took 2140                   
[ 1901.771755] EXT4-fs: mballoc: 18857 preallocated, 11619 discarded            
Checking                                                                        
/dev/ram1: HTREE directory inode 20 has an invalid root node.                   
HTREE INDEX CLEARED.                                                            
/dev/ram1: HTREE directory inode 40 has an invalid root node.                   
HTREE INDEX CLEARED.                                                            
/dev/ram1: Entry 'f15e2' in /work/p0/d5/db/d934 (20) has an incorrect filetype (
was 1, should be 3).                                                            
                                                                                
                                                                                
/dev/ram1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.                         
        (i.e., without -a or -p options)                                        
# fsck /dev/ram1                                      
fsck 1.41.3 (12-Oct-2008)                                                       
e2fsck 1.41.3 (12-Oct-2008)                                                     
/dev/ram1 contains a file system with errors, check forced.                     
Pass 1: Checking inodes, blocks, and sizes                                      
Pass 2: Checking directory structure                                            
Entry 'f15e2' in /work/p0/d5/db/d934 (20) has an incorrect filetype (was 1, shou
ld be 3).                                                                       
Fix<y>? yes                                                                     
                                                                                
Entry 'd51' in /work/p0/d5/db/d934 (20) is a link to directory /work/p0/d5/db/d9
34/d51 (110).                                                                   Clear<y>? yes                                                                   
                                                                                
Entry 'd1cba' in /work/p0/d5/db/d934 (20) is a link to directory /work/p0/d5/db/
d934/d1cba (918).                                                               
Clear<y>? yes                                                                   
                                                                                
Entry 'd17f8' in /work/p0/d5/db/d203c (40) is a link to directory /work/p0/d5/db
/d203c/d17f8 (392).                                                             
Clear<y>? yes                                                                   
                                                                                
Pass 3: Checking directory connectivity                                         
Pass 4: Checking reference counts                                               
Inode 36 ref count is 2, should be 3.  Fix<y>? yes                              
                                                                                
Inode 37 ref count is 2, should be 3.  Fix<y>? yes                              
                                                                                
Inode 55 ref count is 2, should be 3.  Fix<y>? yes                              
                                                                                
.....
                                                                                
Inode 655 ref count is 4, should be 5.  Fix<y>? yes                             
                                                                                Inode 1024 ref count is 4, should be 5.  Fix<y>? yes                            
                                                                                
Pass 5: Checking group summary information                                      
                                                                                
/dev/ram1: ***** FILE SYSTEM WAS MODIFIED *****                                 
/dev/ram1: 1024/1024 files (24.2% non-contiguous), 4096/4096 blocks             

Re: Error testing ext3 on brd ramdisk

[Denis Karpov]

On Fri, Mar 20, 2009 at 02:24:05PM +0200, Denis Karpov wrote:
> Unfortunately it looks like the problem is not fixed - JBD still complains
> and in the end HTREE is getting damaged, in both ext3 and ext4 tests (see
> attached logs).
> 
> Denis

Please, disregard the previos message, I tested with a wrong patchset.
Sorry for the hussle.

Denis

Re: Error testing ext3 on brd ramdisk

[Denis Karpov]

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

On Wed, Mar 18, 2009 at 02:42:02PM +0100, ext Jan Kara wrote:
> > On Tue, Mar 17, 2009 at 11:40:19AM +0200, Denis Karpov wrote:
> > Jan's fixes are here:
> > http://marc.info/?l=linux-ext4&m=123731584711382&w=2
> > It would be interesting to try them, and if they don't work maybe
> > he's also interested so I cc'ed him.

Hello, 

I've re-run the tests (with Jan's patches and also Nick's "fs: new inode
i_state corruption fix" patch).

> > > In both cases I saw some complains from JBD/JBD2:
> > >  JBD: Detected IO errors while flushing file data on
>   Yes, my patches fix exactly this problem. So please try running with
> them. I'm not sure about that HTREE corruption you see during fsck. That
> seems to be a separate issue.

The issue with JBD seems to be gone. But problem with HTREE being corrupted
still remains (see attached logs).

Denis

[-- Attachment #2: ext3.htree.1.txt --]
[-- Type: text/plain, Size: 5241 bytes --]

-------------------------------------------------------------                   
Cycle 26                                                                        
Fri Mar 20 09:23:50 EDT 2009                                                    
Mounting                                                                        
[  907.443733] EXT3 FS on ram0, internal journal                                
[  907.448199] EXT3-fs: mounted filesystem with ordered data mode.              
[  907.448529] kjournald starting.  Commit interval 5 seconds                   
Removing old fsstress data                                                      
Starting fsstress                                                               
Sleeping 30 seconds                                                             
seed = 1237468251                                                               
Stopping fsstress                                                               
 5656 ttyS0    00:00:00 fsstress_ext3                                           
 5659 ttyS0    00:00:26 fsstress_ext3                                           
 5660 ttyS0    00:00:25 fsstress_ext3                                           
 5661 ttyS0    00:00:25 fsstress_ext3                                           
./brd_test_ext3.sh: line 37:  5656 Terminated              `pwd`/fsstress_ext3 -
d $TESTDIR/work -p 3 -l 0 -n 100000000                                          Unmounting                                                                      
Checking                                                                        
/dev/ram0: HTREE directory inode 82 has an invalid root node.                   
HTREE INDEX CLEARED.                                                            
/dev/ram0: Entry 'c17e8' in /work/p1/d2/d99 (82) has an incorrect filetype (was 
3, should be 1).                                                                
                                                                                
                                                                                
/dev/ram0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.                         
        (i.e., without -a or -p options)                                        

# fsck.ext3 /dev/ram0                                 
e2fsck 1.41.3 (12-Oct-2008)                                                     
/dev/ram0 contains a file system with errors, check forced.                     
Pass 1: Checking inodes, blocks, and sizes                                      
Pass 2: Checking directory structure                                            
Entry 'c17e8' in /work/p1/d2/d99 (82) has an incorrect filetype (was 3, should b
e 1).                                                                           
Fix<y>? yes                                                                     
                                                                                
Entry 'fdab' in /work/p1/d2/d99 (82) has an incorrect filetype (was 1, should be
 7).                                                                            
Fix<y>? yes                                                                     
                                                                                
Entry 'c17fa' in /work/p1/d2/d99 (82) has an incorrect filetype (was 3, should be 1).                                                                           
Fix<y>? yes                                                                     
                                                                                
Entry 'da0' in /work/p1/d2/d99 (82) is a link to directory /work/p1/d2/d99/da0 (
238).                                                                           
Clear<y>? yes                                                                   
                                                                                
Pass 3: Checking directory connectivity                                         
Pass 4: Checking reference counts                                               
Inode 83 ref count is 9, should be 10.  Fix<y>? yes                             
                                                                                
Inode 94 ref count is 3, should be 4.  Fix<y>? yes                                                                                                              
Inode 99 ref count is 9, should be 10.  Fix<y>? yes                             
                                                                                ...

Inode 1018 ref count is 2, should be 3.  Fix<y>? yes                            
                                                                                
Inode 1024 ref count is 1, should be 2.  Fix<y>? yes                            
                                                                                
Pass 5: Checking group summary information                                      
                                                                                
/dev/ram0: ***** FILE SYSTEM WAS MODIFIED *****                                 
/dev/ram0: 1024/1024 files (12.0% non-contiguous), 4096/4096 blocks             

[-- Attachment #3: ext4.htree.1.txt --]
[-- Type: text/plain, Size: 2178 bytes --]

-------------------------------------------------------------
Cycle 5
Fri Mar 20 09:17:50 EDT 2009
Mounting
Removing old fsstress data
Starting fsstress
Sleeping 30 seconds
seed = 1237604365
Stopping fsstress
 5370 pts/0    00:00:00 fsstress_ext4
 5373 pts/0    00:00:19 fsstress_ext4
 5374 pts/0    00:00:20 fsstress_ext4
 5375 pts/0    00:00:19 fsstress_ext4
./brd_test_ext4.sh: line 36:  5370 Terminated              `pwd`/fsstress_ext4 -d $TESTDIR/work -p 3 -l 0 -n 100000000
Unmounting
Checking
/dev/ram1: HTREE directory inode 165 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram1: HTREE directory inode 272 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram1: Entry 'c363' in /work/p2/d2/de/d5f/d80/d616 (272) has an incorrect filetype (was 3, should be 1).


/dev/ram1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)
# fsck.ext4 /dev/ram1
e2fsck 1.41.3 (12-Oct-2008)
/dev/ram1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'c363' in /work/p2/d2/de/d5f/d80/d616 (272) has an incorrect filetype (was 3, should be 1).
Fix<y>? yes

Entry 'c10b5' in /work/p2/d2/de/d37 (165) has an incorrect filetype (was 3, should be 1).
Fix<y>? yes

Entry 'f164' in /work/p2/d2/de/d37 (165) has an incorrect filetype (was 1, should be 3).
Fix<y>? yes

Entry 'f104e' in /work/p2/d2/de/d37 (165) has an incorrect filetype (was 1, should be 2).
Fix<y>? yes

Entry 'deaa' in /work/p2/d2/de/d5f/d80/d616 (272) is a link to directory /work/p2/d2/de/d5f/d80/d616/deaa (819).
Clear<y>? yes

Entry 'd155a' in /work/p2/d2/de/d37 (165) is a link to directory /work/p2/d2/de/d37/d155a (434).
Clear<y>? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 25 ref count is 6, should be 7.  Fix<y>? yes

Inode 48 ref count is 1, should be 2.  Fix<y>? yes

...

Inode 1003 ref count is 3, should be 4.  Fix<y>? yes

Inode 1004 ref count is 1, should be 2.  Fix<y>? yes

Pass 5: Checking group summary information

/dev/ram1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/ram1: 1024/1024 files (20.5% non-contiguous), 4096/4096 blocks

Re: Error testing ext3 on brd ramdisk

[Nick Piggin]

On Thu, Mar 05, 2009 at 10:19:46AM +0100, Jorge Boncompte [DTI2] wrote:
> -----------
> umount /etc (/etc is what is mounted from /dev/ram0)
> dd if=/dev/zero of=/dev/ram0 bs=1k count=1000
> mount /dev/ram0 /etc -t minix -o rw
> -----------
> ...succeds and mounts a corrupted filesystem with the old content. Doing 
> the same with the all ramdisk driver fails on mount with "no filesystem 
> found".
> 
> If I do...
> -----------
> umount /etc (/etc is what is mounted from /dev/ram0)
> echo 3 > /proc/sys/vm/drop_caches
> dd if=/dev/zero of=/dev/ram0 bs=1k count=1000
> mount /dev/ram0 /etc -t minix -o rw
> ----------
> ... then the mount fails with no filesystem found as it should.

I can't reproduce this. Is the filesystem definitely being
unmounted and nothing else is holding the bdev inode open?

I can only imagine something like this happening if the fs
is still mounted, in which case it will write back some
superblock over the zeroed bdev, possibly allowing it to mount
again, or if the zeroed writes somehow get lost, which would
seem like a problem with the buffer cache.

Actually, the 2nd scenario is more likely, because you wouldn't
see it with the old rd driver because it never allows the buffer
cache to be freed.

Are you getting any errors in your dmesg or anything like that?

What happens when you run the following patch? Can you run the
test case then when you reproduce the problem, see if anything is
in dmesg?

Thanks,
Nick

---
 fs/block_dev.c |    3 +++
 fs/buffer.c    |    4 +++-
 mm/filemap.c   |   29 ++++++++++++-----------------
 3 files changed, 18 insertions(+), 18 deletions(-)

Index: linux-2.6/mm/filemap.c
===================================================================
--- linux-2.6.orig/mm/filemap.c
+++ linux-2.6/mm/filemap.c
@@ -394,18 +394,14 @@ int filemap_write_and_wait(struct addres
 	int err = 0;
 
 	if (mapping->nrpages) {
+		int err2;
+
 		err = filemap_fdatawrite(mapping);
-		/*
-		 * Even if the above returned error, the pages may be
-		 * written partially (e.g. -ENOSPC), so we wait for it.
-		 * But the -EIO is special case, it may indicate the worst
-		 * thing (e.g. bug) happened, so we avoid waiting for it.
-		 */
-		if (err != -EIO) {
-			int err2 = filemap_fdatawait(mapping);
-			if (!err)
-				err = err2;
-		}
+		WARN_ON(err);
+		err2 = filemap_fdatawait(mapping);
+		WARN_ON(err2);
+		if (!err)
+			err = err2;
 	}
 	return err;
 }
@@ -428,16 +424,15 @@ int filemap_write_and_wait_range(struct
 	int err = 0;
 
 	if (mapping->nrpages) {
+		int err2;
+
 		err = __filemap_fdatawrite_range(mapping, lstart, lend,
 						 WB_SYNC_ALL);
-		/* See comment of filemap_write_and_wait() */
-		if (err != -EIO) {
-			int err2 = wait_on_page_writeback_range(mapping,
+		err2 = wait_on_page_writeback_range(mapping,
 						lstart >> PAGE_CACHE_SHIFT,
 						lend >> PAGE_CACHE_SHIFT);
-			if (!err)
-				err = err2;
-		}
+		if (!err)
+			err = err2;
 	}
 	return err;
 }
Index: linux-2.6/fs/block_dev.c
===================================================================
--- linux-2.6.orig/fs/block_dev.c
+++ linux-2.6/fs/block_dev.c
@@ -66,6 +66,7 @@ static void kill_bdev(struct block_devic
 		return;
 	invalidate_bh_lrus();
 	truncate_inode_pages(bdev->bd_inode->i_mapping, 0);
+	printk("truncated bdev\n");
 }	
 
 int set_blocksize(struct block_device *bdev, int size)
@@ -80,6 +81,7 @@ int set_blocksize(struct block_device *b
 
 	/* Don't change the size if it is same as current */
 	if (bdev->bd_block_size != size) {
+		printk("killing bdev\n");
 		sync_blockdev(bdev);
 		bdev->bd_block_size = size;
 		bdev->bd_inode->i_blkbits = blksize_bits(size);
@@ -1177,6 +1179,7 @@ static int __blkdev_put(struct block_dev
 		bdev->bd_part_count--;
 
 	if (!--bdev->bd_openers) {
+		printk("killing bdev\n");
 		sync_blockdev(bdev);
 		kill_bdev(bdev);
 	}
Index: linux-2.6/fs/buffer.c
===================================================================
--- linux-2.6.orig/fs/buffer.c
+++ linux-2.6/fs/buffer.c
@@ -173,8 +173,10 @@ int sync_blockdev(struct block_device *b
 {
 	int ret = 0;
 
-	if (bdev)
+	if (bdev) {
+		printk("syncing bdev\n");
 		ret = filemap_write_and_wait(bdev->bd_inode->i_mapping);
+	}
 	return ret;
 }
 EXPORT_SYMBOL(sync_blockdev);

Re: Error testing ext3 on brd ramdisk

[Jorge Boncompte [DTI2]]

Nick Piggin escribió:
> On Thu, Mar 05, 2009 at 10:19:46AM +0100, Jorge Boncompte [DTI2] wrote:
>> -----------
>> umount /etc (/etc is what is mounted from /dev/ram0)
>> dd if=/dev/zero of=/dev/ram0 bs=1k count=1000
>> mount /dev/ram0 /etc -t minix -o rw
>> -----------
>> ...succeds and mounts a corrupted filesystem with the old content. Doing 
>> the same with the all ramdisk driver fails on mount with "no filesystem 
>> found".
>>
>> If I do...
>> -----------
>> umount /etc (/etc is what is mounted from /dev/ram0)
>> echo 3 > /proc/sys/vm/drop_caches
>> dd if=/dev/zero of=/dev/ram0 bs=1k count=1000
>> mount /dev/ram0 /etc -t minix -o rw
>> ----------
>> ... then the mount fails with no filesystem found as it should.
> 
> I can't reproduce this. Is the filesystem definitely being
> unmounted and nothing else is holding the bdev inode open?

	I don't know about the bdev inode :-( but I am sure that in 
/proc/mounts does not appear as listed.

> I can only imagine something like this happening if the fs
> is still mounted, in which case it will write back some
> superblock over the zeroed bdev, possibly allowing it to mount
> again, or if the zeroed writes somehow get lost, which would
> seem like a problem with the buffer cache.
> 
> Actually, the 2nd scenario is more likely, because you wouldn't
> see it with the old rd driver because it never allows the buffer
> cache to be freed.
> 
> Are you getting any errors in your dmesg or anything like that?

	No until I try to mount the filesystem again, then minix starts to 
complain.
-----------------
minix_free_block (ram0:38): bit already cleared
init_special_inode: bogus i_mode (0)
init_special_inode: bogus i_mode (0)
init_special_inode: bogus i_mode (0)
init_special_inode: bogus i_mode (0)
init_special_inode: bogus i_mode (0)
.........
-----------------

> What happens when you run the following patch? Can you run the
> test case then when you reproduce the problem, see if anything is
> in dmesg?

After a successful save
------------------
Mar  5 13:34:34 system: configuration save requested by user=root
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:34 kernel: killing bdev
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:34 kernel: truncated bdev
Mar  5 13:34:34 kernel: killing bdev
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:34 kernel: truncated bdev
Mar  5 13:34:34 kernel: killing bdev
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:34 kernel: truncated bdev
Mar  5 13:34:34 kernel: killing bdev
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:34 kernel: truncated bdev
Mar  5 13:34:34 kernel: killing bdev
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:34 kernel: truncated bdev
Mar  5 13:34:34 kernel: killing bdev
Mar  5 13:34:34 kernel: syncing bdev
Mar  5 13:34:35 kernel: truncated bdev
Mar  5 13:34:35 kernel: killing bdev
Mar  5 13:34:35 kernel: syncing bdev
Mar  5 13:34:35 kernel: truncated bdev
Mar  5 13:34:35 kernel: killing bdev
Mar  5 13:34:35 kernel: syncing bdev
Mar  5 13:34:35 kernel: truncated bdev
------------------

rm -f <some archives>

------------------
Mar  5 13:35:00 system: configuration save requested by user=root
Mar  5 13:35:00 kernel: syncing bdev
Mar  5 13:35:00 kernel: syncing bdev
Mar  5 13:35:00 kernel: syncing bdev
Mar  5 13:35:00 kernel: syncing bdev
------------------

-- 
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be made.
==============================================================

Re: Error testing ext3 on brd ramdisk

[Adrian Hunter]

Nick Piggin wrote:
> On Mon, Mar 02, 2009 at 06:42:18PM +0100, Jorge Boncompte [DTI2] wrote:
>> Nick Piggin escribió:
>>> On Fri, Feb 27, 2009 at 07:08:46PM +0100, Jorge Boncompte [DTI2] wrote:
>>>> 	Hi,
>>>>
>>>> 	I have added Nick Piggin to the CC: as maintainer of the brd driver.
>>>>
>>>> 	After switching an embedded distribution that /etc on a ramdisk 
>>>> 	based minix filesystem from 2.6.23.17 to 2.6.29-rcX i am too getting 
>>>> 	errors ant the filesystem is corrupted. Does not happen always. The 
>>>> visible effect with text files after reboot is getting the old version of 
>>>> the file and "\0"'s at the end.
>>>>
>>>> 	Did you found a solution?
>>> What architectures are you using? It's possible that brd is missing
>>> a cacheflush. I test it pretty heavily on x86 and no problems, so
>>> this might point to an arch specific problem.
>>>
>>> ---
>>> drivers/block/brd.c |    4 +++-
>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> Index: linux-2.6/drivers/block/brd.c
>>> ===================================================================
>>> --- linux-2.6.orig/drivers/block/brd.c
>>> +++ linux-2.6/drivers/block/brd.c
>>> @@ -275,8 +275,10 @@ static int brd_do_bvec(struct brd_device
>>> 	if (rw == READ) {
>>> 		copy_from_brd(mem + off, brd, sector, len);
>>> 		flush_dcache_page(page);
>>> -	} else
>>> +	} else {
>>> +		flush_dcache_page(page);
>>> 		copy_to_brd(brd, mem + off, sector, len);
>>> +	}
>>> 	kunmap_atomic(mem, KM_USER0);
>>>
>>> out:
>> 	Hi, I am on 32bits x86, 2 x Xeon with HT CPUs, but I have seen the 
>> 	same corruption on a KVM/QEMU guest with single emulated CPU.
>>
>> 	With your patch on top of vanilla 2.6.29-rc3+plus some networking 
>> patches I still get corruption sometimes.
>>
>> 	The script that saves the configuration does...
>>
>> ------------
>> mount -no remount,ro /dev/ram0
>> dd if=/dev/ram0 of=config.bin bs=1k count=1000
>> mount -no remount,rw /dev/ram0
>> md5sum config.bin
>> dd if=config.bin of=/dev/hda1
>> echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
>> ------------
>>
>> on system boot
>>
>> ------------
>> CHECK MD5SUM
>> dd if=/dev/hda1 of=/dev/ram0 bs=1k count=1000
>> fsck.minix -a /dev/ram0
>> mount -nt minix /dev/ram0 /etc -o rw
>> ------------
>>
>> 	I have never seen a MD5 failure on boot, just sometimes the 
>> 	filesystem is corrupted. Kernel config attached.
> 
> Hi Jorge,
> 
> Well I found and fixed something :) (see other mail) but I don't know
> whether that applies to you here if you're running with a single CPU
> and no preemption. But still, it might be worth trying that patch? I'm
> sorry I'm still unable to reproduce a problem with your script
> (although you don't describe how you create the filesystem before
> you remount it).
> 
>>From your description, it suggests that the corrupted image is being
> read from /dev/ram0 (becuase the md5sum passes).
> 
> In your script, can you run fsck.minix on config.bin when you first
> create it? What if you unmount /dev/ram0 before copying the image?
> 
> Thanks,
> Nick

Thanks for looking at this.

I applied both patches and still got:

-------------------------------------------------------------
Cycle 616
Thu Mar  5 22:13:16 EET 2009
Mounting
kjournald starting.  Commit interval 5 seconds
EXT3 FS on ram0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Removing old fsstress data
Starting fsstress
Sleeping 30 seconds
seed = 1237038794
Stopping fsstress
18670 ttyS0    00:00:00 fsstress
18672 ttyS0    00:00:15 fsstress
18673 ttyS0    00:00:15 fsstress
18674 ttyS0    00:00:15 fsstress
./brd-test.sh: line 30: 18670 Terminated              ./fsstress/fsstress -d /mnt/test_file_system/work -p 3 -l 0 -n 100000000
Unmounting
Checking
/dev/ram0: HTREE directory inode 46 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram0: Entry 'f6c' in /work/p1/d0 (46) has deleted/unused inode 261.  CLEARED.
/dev/ram0: Entry 'f276' in /work/p1/d0 (46) has deleted/unused inode 454.  CLEARED.
/dev/ram0: Entry 'f152' in /work/p1/d0 (46) has deleted/unused inode 543.  CLEARED.
/dev/ram0: Entry 'cc1' in /work/p1/d0 (46) has an incorrect filetype (was 3, should be 2).


/dev/ram0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)



My test box is Pentium D dual core.

Re: Error testing ext3 on brd ramdisk

[Nick Piggin]

On Fri, Mar 06, 2009 at 09:47:32AM +0200, Adrian Hunter wrote:
> Nick Piggin wrote:
> >On Mon, Mar 02, 2009 at 06:42:18PM +0100, Jorge Boncompte [DTI2] wrote:
> >>Nick Piggin escribió:
> >>>On Fri, Feb 27, 2009 at 07:08:46PM +0100, Jorge Boncompte [DTI2] wrote:
> >>>>	Hi,
> >>>>
> >>>>	I have added Nick Piggin to the CC: as maintainer of the brd driver.
> >>>>
> >>>>	After switching an embedded distribution that /etc on a ramdisk 
> >>>>	based minix filesystem from 2.6.23.17 to 2.6.29-rcX i am too getting 
> >>>>	errors ant the filesystem is corrupted. Does not happen always. The 
> >>>>visible effect with text files after reboot is getting the old version 
> >>>>of the file and "\0"'s at the end.
> >>>>
> >>>>	Did you found a solution?
> >>>What architectures are you using? It's possible that brd is missing
> >>>a cacheflush. I test it pretty heavily on x86 and no problems, so
> >>>this might point to an arch specific problem.
> >>>
> >>>---
> >>>drivers/block/brd.c |    4 +++-
> >>>1 file changed, 3 insertions(+), 1 deletion(-)
> >>>
> >>>Index: linux-2.6/drivers/block/brd.c
> >>>===================================================================
> >>>--- linux-2.6.orig/drivers/block/brd.c
> >>>+++ linux-2.6/drivers/block/brd.c
> >>>@@ -275,8 +275,10 @@ static int brd_do_bvec(struct brd_device
> >>>	if (rw == READ) {
> >>>		copy_from_brd(mem + off, brd, sector, len);
> >>>		flush_dcache_page(page);
> >>>-	} else
> >>>+	} else {
> >>>+		flush_dcache_page(page);
> >>>		copy_to_brd(brd, mem + off, sector, len);
> >>>+	}
> >>>	kunmap_atomic(mem, KM_USER0);
> >>>
> >>>out:
> >>	Hi, I am on 32bits x86, 2 x Xeon with HT CPUs, but I have seen the 
> >>	same corruption on a KVM/QEMU guest with single emulated CPU.
> >>
> >>	With your patch on top of vanilla 2.6.29-rc3+plus some networking 
> >>patches I still get corruption sometimes.
> >>
> >>	The script that saves the configuration does...
> >>
> >>------------
> >>mount -no remount,ro /dev/ram0
> >>dd if=/dev/ram0 of=config.bin bs=1k count=1000
> >>mount -no remount,rw /dev/ram0
> >>md5sum config.bin
> >>dd if=config.bin of=/dev/hda1
> >>echo $md5sum | dd of=/dev/hda1 bs=1k seek=1100 count=32
> >>------------
> >>
> >>on system boot
> >>
> >>------------
> >>CHECK MD5SUM
> >>dd if=/dev/hda1 of=/dev/ram0 bs=1k count=1000
> >>fsck.minix -a /dev/ram0
> >>mount -nt minix /dev/ram0 /etc -o rw
> >>------------
> >>
> >>	I have never seen a MD5 failure on boot, just sometimes the 
> >>	filesystem is corrupted. Kernel config attached.
> >
> >Hi Jorge,
> >
> >Well I found and fixed something :) (see other mail) but I don't know
> >whether that applies to you here if you're running with a single CPU
> >and no preemption. But still, it might be worth trying that patch? I'm
> >sorry I'm still unable to reproduce a problem with your script
> >(although you don't describe how you create the filesystem before
> >you remount it).
> >
> >>From your description, it suggests that the corrupted image is being
> >read from /dev/ram0 (becuase the md5sum passes).
> >
> >In your script, can you run fsck.minix on config.bin when you first
> >create it? What if you unmount /dev/ram0 before copying the image?
> >
> >Thanks,
> >Nick
> 
> Thanks for looking at this.
> 
> I applied both patches and still got:

Hi Adrian,

Thanks for testing... it does seem like the same problem as Jorge has
(inconsistent filesystem metadata / block device contents at unmount).

I'll keep working at it...

Thanks,
Nick