Re: BUG_ON at mballoc.c:3752
* Eric Sandeen ([EMAIL PROTECTED]) wrote: Eric Sesterhenn wrote: Eric , can you run the test with below patch and see if this makes any difference ?. I know we are not fixing any bugs in the below patch. ok, i checked out the old version again and applied both patches, the BUG is gone (no surprise) In the case where it would have hit the BUG i now get the following message: [ 740.400288] Aborting journal on device loop0. No message before that about *why* it aborted? assumed the stuff was from the previous runs [ 113.318700] Aborting journal on device loop0. [ 113.324237] ext4_abort called. [ 113.324312] EXT4-fs error (device loop0): ext4_journal_start_sb: Detected aborted journal [ 113.324394] Remounting filesystem read-only [ 113.330324] EXT4-fs error (device loop0) in ext4_dirty_inode: IO failure [ 113.330438] EXT4-fs error (device loop0) in ext4_ordered_write_end: IO failure [ 114.884485] EXT4-fs error (device loop0): ext4_mb_generate_buddy: EXT4-fs: group 0: 6590 blocks in bitmap, 6600 in gd [ 116.193424] Aborting journal on device loop0. [ 116.196910] ext4_abort called. [ 116.197064] EXT4-fs error (device loop0): ext4_journal_start_sb: Detected aborted journal [ 116.197147] Remounting filesystem read-only [ 118.031066] EXT4-fs error (device loop0): ext4_mb_generate_buddy: EXT4-fs: group 0: 6590 blocks in bitmap, 6600 in gd [ 119.692812] Buffer I/O error on device loop0, logical block 20729 [ 121.968397] Buffer I/O error on device loop0, logical block 20729 [ 123.124070] Aborting journal on device loop0. [ 123.125550] ext4_abort called. [ 123.125654] EXT4-fs error (device loop0): ext4_journal_start_sb: Detected aborted journal [ 123.125736] Remounting filesystem read-only [ 123.145792] pa cba56770: logic 32, phys. 3649, len 32 [ 123.145861] EXT4-fs error (device loop0): ext4_mb_release_inode_pa: free 30, pa_free 29 [ 123.145943] EXT4-fs error (device loop0) in ext4_mb_free_blocks: Journal has aborted [ 123.153174] EXT4-fs error (device loop0) in ext4_dirty_inode: IO failure [ 123.153287] EXT4-fs error (device loop0) in ext4_reserve_inode_write: Journal has aborted [ 123.153363] pa cba56198: logic 16, phys. 2113, len 16 [ 123.153387] EXT4-fs error (device loop0): ext4_mb_release_inode_pa: free 15, pa_free 14 [ 123.153488] EXT4-fs error (device loop0) in ext4_mb_free_blocks: Journal has aborted [ 125.193083] EXT4-fs error (device loop0): ext4_mb_generate_buddy: EXT4-fs: group 0: 6590 blocks in bitmap, 6600 in gd [ 127.683441] Aborting journal on device loop0. [ 127.685090] EXT4-fs error (device loop0) in ext4_reserve_inode_write: Journal has aborted [ 127.687548] pa cba56330: logic 16, phys. 1969, len 16 [ 127.687585] EXT4-fs error (device loop0): ext4_mb_release_inode_pa: free 16, pa_free 15 [ 127.687687] BUG: sleeping function called from invalid context at include/linux/buffer_head.h:325 [ 127.688494] BUG: scheduling while atomic: fstest/4447/0x0002 [ 127.712616] EXT4-fs error (device loop0) in ext4_reserve_inode_write: Journal has aborted [ 127.713055] BUG: scheduling while atomic: fstest/4447/0x0002 [ 127.715557] EXT4-fs error (device loop0) in ext4_orphan_add: Journal has aborted [ 127.735782] EXT4-fs error (device loop0) in ext4_reserve_inode_write: Journal has aborted [ 127.735883] BUG: scheduling while atomic: fstest/4447/0x0002 [ 127.736851] EXT4-fs error (device loop0) in ext4_setattr: Journal has aborted [ 127.758924] ext4_abort called. [ 127.759044] EXT4-fs error (device loop0): ext4_journal_start_sb: Detected aborted journal [ 127.759125] Remounting filesystem read-only [ 127.762504] EXT4-fs error (device loop0) in ext4_mb_free_blocks: Journal has aborted [ 130.003586] EXT4-fs error (device loop0): ext4_mb_generate_buddy: EXT4-fs: group 0: 6590 blocks in bitmap, 6600 in gd [ 133.104600] Aborting journal on device loop0. [ 133.109459] ext4_abort called. [ 133.109528] EXT4-fs error (device loop0): ext4_journal_start_sb: Detected aborted journal [ 133.109683] Remounting filesystem read-only [ 133.128537] EXT4-fs error (device loop0) in ext4_dirty_inode: IO failure [ 133.128766] EXT4-fs error (device loop0) in ext4_reserve_inode_write: Journal has aborted [ 133.128803] EXT4-fs error (device loop0) in ext4_mb_free_blocks: Journal has aborted [ 135.037160] EXT4-fs error (device loop0): ext4_mb_generate_buddy: EXT4-fs: group 0: 6590 blocks in bitmap, 6600 in gd [ 135.995986] Aborting journal on device loop0. [ 135.77] ext4_abort called. [ 136.49] EXT4-fs error (device loop0): ext4_journal_start_sb: Detected aborted journal [ 136.000129] Remounting filesystem read-only [ 136.005258] pa cba56440: logic 32, phys. 2081, len 32 [ 136.005312] EXT4-fs error (device loop0): ext4_mb_release_inode_pa: free 30, pa_free 29 [ 136.005478] EXT4-fs error (device loop0) in ext4_mb_free_blocks: Journal has aborted [ 136.011164] EXT4-fs error (device loop0) in ext4_reserve_inode_write: Journal has aborted
Re: BUG_ON at mballoc.c:3752
Eric , can you run the test with below patch and see if this makes any difference ?. I know we are not fixing any bugs in the below patch. ok, i checked out the old version again and applied both patches, the BUG is gone (no surprise) In the case where it would have hit the BUG i now get the following message: [ 740.400288] Aborting journal on device loop0. [ 740.405032] ext4_abort called. [ 740.405097] EXT4-fs error (device loop0): ext4_journal_start_sb: Detected aborted journal [ 740.405178] Remounting filesystem read-only [ 740.410974] EXT4-fs error (device loop0) in ext4_ordered_write_end: IO failure [ 740.414300] EXT4-fs error (device loop0) in ext4_reserve_inode_write: Journal has aborted [ 740.414422] pa cba56990: logic 16, phys. 1953, len 16 [ 740.414447] EXT4-fs error (device loop0): ext4_mb_release_inode_pa: free 4, pa_free 3 [ 740.414548] EXT4-fs error (device loop0) in ext4_mb_free_blocks: Journal has aborted Greetings, Eric - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: BUG_ON at mballoc.c:3752
* Aneesh Kumar K.V ([EMAIL PROTECTED]) wrote: On Wed, Feb 06, 2008 at 03:59:48PM -0600, Dave Kleikamp wrote: File systems should not call BUG() due to a corrupt file system. Instead the code should fail the operation, possibly marking the file system read-only (or panicking) depending on the errors= mount option. Eric Sandeen explained me the same on IRC. I was busy with the migrate locking bug. That's why i didn't update here. Today i tried to reproduce the problem using the image provided. But in my case it is not hitting the BUG_ON (mostly due to single cpu). I did look at the code and am not still not clear how we can hit that BUG_ON. prealloc free space pa_free is generated out of bitmap. So only if something corrupted bitmap after we initialized prealloc space we will hit this case. In mballoc we error out if the block allocated or fall in system zone. One thing i noticed is, the journal is corrupt. So the only possibility that i have is journal write resulted in bitmap corruption. I also looked at the mballoc to make sure we don't panic in case of a corrupt bitmap. Below is the patch that i have now. This one is yet to go through the ABAT test but it would be nice to see whether the below change cause any other issues. Eric , can you run the test with below patch and see if this makes any difference ?. I know we are not fixing any bugs in the below patch. hi, so far i am not able to reproduce this on 2.6.24-08039-g488b5ec neither with the ext4-fix-null-pointer-deref-in-journal_wait_on_commit_record.patch nor without it. I will try 2.6.24-05749-g8af03e7 with the patch and your change later today. Greetings, Eric - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: BUG_ON at mballoc.c:3752
* Aneesh Kumar K.V ([EMAIL PROTECTED]) wrote: On Thu, Jan 31, 2008 at 04:42:07PM +0100, Eric Sesterhenn wrote: * Eric Sesterhenn ([EMAIL PROTECTED]) wrote: hi, while running a modified version of fsfuzzer i triggered the BUG() in ext4_mb_release_inode_pa(). Sadly I am not able to reproduce this using the generated image, but running the fuzzer will usually trigger this in less than 40 attempts. Increasing the JBD2 Debug level didnt give more information. The kernel is current git with ext4-fix-null-pointer-deref-in-journal_wait_on_commit_record.patch applied. I am now able to reproduce this using this image: http://www.cccmz.de/~snakebyte/ext4.24.img.bz2 the following commands will trigger the oops for me mount cfs/ext4.24.img /media/test -t ext4dev -o extents -o loop mkdir /media/test/stress chown snakebyte:snakebyte /media/test/stress sudo -u snakebyte fstest -n 10 -l 10 -f 5 -s 4 -p /media/test/stress/ The file system is corrupted. The BUG_ON indicate that the free spcae marked in the prealloc space and found by looking at the bitmap are not same. Do you have a set of steps that i can follow to reproduce this ? just compile the mangle.c and run the modified fuzzer for a while (link below) or use the steps above on a clean file system ? had no luck on a clean fs with this Where do i find the fsfuzzer that you are using ? http://www.cccmz.de/~snakebyte/fsfuzzer-0.6-lmh-eric.tar.bz2 http://www.cccmz.de/~snakebyte/fsfuzz.diff needs user/group nobody:nobody and stuff like fstest, fsx, iozone, fsstress The changes i made are basically changing the fuzzing ratio, adding udf, hfsplus and ext4, reducing the number of runs to 100 (not unlimited), saving a backup of the image before mounting and running the tests, and mounting ext3 with -o debug Greetings, Eric - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fw: [Bugme-new] [Bug 9849] New: NULL pointer deref in journal_wait_on_commit_record
* Mingming Cao ([EMAIL PROTECTED]) wrote: We need to check the error returns from journal_submit_commit_record() and avoid calling journal_wait_on_commit_record() in the failure case. Signed-off-by: Mingming Cao [EMAIL PROTECTED] thanks, the patch works for me, i closed the bugzilla entry - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
BUG_ON at mballoc.c:3752
hi, while running a modified version of fsfuzzer i triggered the BUG() in ext4_mb_release_inode_pa(). Sadly I am not able to reproduce this using the generated image, but running the fuzzer will usually trigger this in less than 40 attempts. Increasing the JBD2 Debug level didnt give more information. The kernel is current git with ext4-fix-null-pointer-deref-in-journal_wait_on_commit_record.patch applied. Greetings, Eric [ 1570.971980] EXT4-fs error (device loop0) in ext4_reserve_inode_write: Journal has aborted [ 1570.972077] pa c6512330: logic 16, phys. 2337, len 16 [ 1570.972103] free 2, pa_free 1 [ 1570.972191] [ cut here ] [ 1570.972217] kernel BUG at fs/ext4/mballoc.c:3752! [ 1570.972241] invalid opcode: [#1] PREEMPT DEBUG_PAGEALLOC [ 1570.972386] Modules linked in: [ 1570.972425] [ 1570.972509] Pid: 6629, comm: fstest Not tainted (2.6.24-05749-g8af03e7-dirty #19) [ 1570.972534] EIP: 0060:[c02266b9] EFLAGS: 00010202 CPU: 0 [ 1570.972570] EIP is at ext4_mb_release_inode_pa+0x169/0x1a0 [ 1570.972595] EAX: 0001 EBX: 0930 ECX: 0001 EDX: 0001 [ 1570.972678] ESI: 0930 EDI: c6512330 EBP: cb638b28 ESP: cb638a84 [ 1570.972703] DS: 007b ES: 007b FS: GS: 0033 SS: 0068 [ 1570.972728] Process fstest (pid: 6629, ti=cb638000 task=cb698000 task.ti=cb638000) [ 1570.972751] Stack: c07c21bb 0002 0001 0921 0010 cbff34e0 cb638b54 0002 [ 1570.972899]cb5fa430 c64824a0 cb5fb920 0022 cbff34e0 cb638ad4 0246 0400 [ 1570.972899]cbfa2000 cb5fb920 cbff34e0 092e 0002 cbfa2000 [ 1570.972899] Call Trace: [ 1570.972899] [c020e3a4] ? read_block_bitmap+0x54/0x120 [ 1570.972899] [c022bd24] ? ext4_mb_discard_inode_preallocations+0x124/0x300 [ 1570.972899] [c022bda5] ? ext4_mb_discard_inode_preallocations+0x1a5/0x300 [ 1570.972899] [c0223577] ? ext4_ext_get_blocks+0x3a7/0x4b0 [ 1570.972899] [c0213928] ? ext4_get_blocks_wrap+0xe8/0x130 [ 1570.972899] [c0213bce] ? ext4_get_block+0x7e/0xf0 [ 1570.972899] [c019d7ba] ? __block_prepare_write+0x17a/0x3a0 [ 1570.972899] [c019da68] ? block_write_begin+0x48/0xe0 [ 1570.972899] [c0213b50] ? ext4_get_block+0x0/0xf0 [ 1570.972899] [c0215127] ? ext4_write_begin+0xb7/0x190 [ 1570.972899] [c0213b50] ? ext4_get_block+0x0/0xf0 [ 1570.972899] [c01557e9] ? generic_perform_write+0xa9/0x190 [ 1570.972899] [c01575bd] ? generic_file_buffered_write+0x6d/0x130 [ 1570.972899] [c01578c1] ? __generic_file_aio_write_nolock+0x241/0x550 [ 1570.972899] [c0144b44] ? trace_hardirqs_on+0xc4/0x150 [ 1570.972899] [c0157c2c] ? generic_file_aio_write+0x5c/0xd0 [ 1570.972899] [c015ab0d] ? free_one_page+0x1ed/0x220 [ 1570.972899] [c0210410] ? ext4_file_write+0x50/0x160 [ 1570.972899] [c017b11d] ? do_sync_write+0xcd/0x110 [ 1570.972899] [c01096f9] ? native_sched_clock+0x69/0xc0 [ 1570.972899] [c01373c0] ? autoremove_wake_function+0x0/0x50 [ 1570.972899] [c01070e5] ? do_softirq+0x55/0xd0 [ 1570.972899] [c01050d3] ? restore_nocheck+0x12/0x15 [ 1570.972899] [c0144b44] ? trace_hardirqs_on+0xc4/0x150 [ 1570.972899] [c017b959] ? vfs_write+0x99/0x130 [ 1570.972899] [c017b050] ? do_sync_write+0x0/0x110 [ 1570.972899] [c017c048] ? sys_pwrite64+0x68/0x70 [ 1570.972899] [c0104fea] ? sysenter_past_esp+0x5f/0xa5 [ 1570.972899] === [ 1570.972899] Code: ff 0f b7 47 4e 89 44 24 08 8b 85 78 ff ff ff c7 04 24 bb 21 7c c0 89 44 24 04 e8 c3 e0 ef ff 0f b7 47 4e 39 85 78 ff ff ff 74 07 0f 0b eb fe 8d 76 00 8b 85 78 ff ff ff 8b 95 7c ff ff ff 01 82 [ 1570.972899] EIP: [c02266b9] ext4_mb_release_inode_pa+0x169/0x1a0 SS:ESP 0068:cb638a84 [ 1570.972942] ---[ end trace 51819e80cd9431da ]--- [ 1570.972969] note: fstest[6629] exited with preempt_count 1 [ 1570.973013] BUG: sleeping function called from invalid context at kernel/rwsem.c:21 [ 1570.973039] in_atomic():1, irqs_disabled():0 [ 1570.973077] INFO: lockdep is turned off. [ 1570.973104] Pid: 6629, comm: fstest Tainted: G D 2.6.24-05749-g8af03e7-dirty #19 [ 1570.973159] [c011e1a6] __might_sleep+0xc6/0xf0 [ 1570.973224] [c06b2c99] down_read+0x19/0x80 [ 1570.973295] [c013a7fd] ? hrtimer_try_to_cancel+0x3d/0x80 [ 1570.973396] [c0125a27] exit_mm+0x27/0xd0 [ 1570.973467] [c01272f3] do_exit+0x133/0x2e0 [ 1570.973529] [c010611c] die+0x13c/0x140 [ 1570.973590] [c0135197] ? search_exception_tables+0x27/0x30 [ 1570.973993] [c01061b1] do_trap+0x91/0xc0 [ 1570.974054] [c0106440] ? do_invalid_op+0x0/0xa0 [ 1570.974133] [c01064c9] do_invalid_op+0x89/0xa0 [ 1570.974195] [c02266b9] ? ext4_mb_release_inode_pa+0x169/0x1a0 [ 1570.974290] [c012007b] ? account_system_time+0x9b/0xd0 [ 1570.974370] [c01245de] ? vprintk+0x1ce/0x360 [ 1570.974465] [c06b4492] error_code+0x6a/0x70 [ 1570.974531] [c012007b] ? account_system_time+0x9b/0xd0 [ 1570.974626] [c02266b9] ? ext4_mb_release_inode_pa+0x169/0x1a0 [ 1570.974707] [c020e3a4] ? read_block_bitmap+0x54/0x120 [ 1570.974803] [c022bd24] ?
Re: BUG_ON at mballoc.c:3752
* Eric Sesterhenn ([EMAIL PROTECTED]) wrote: hi, while running a modified version of fsfuzzer i triggered the BUG() in ext4_mb_release_inode_pa(). Sadly I am not able to reproduce this using the generated image, but running the fuzzer will usually trigger this in less than 40 attempts. Increasing the JBD2 Debug level didnt give more information. The kernel is current git with ext4-fix-null-pointer-deref-in-journal_wait_on_commit_record.patch applied. I am now able to reproduce this using this image: http://www.cccmz.de/~snakebyte/ext4.24.img.bz2 the following commands will trigger the oops for me mount cfs/ext4.24.img /media/test -t ext4dev -o extents -o loop mkdir /media/test/stress chown snakebyte:snakebyte /media/test/stress sudo -u snakebyte fstest -n 10 -l 10 -f 5 -s 4 -p /media/test/stress/ The between the chown and fstest seems necessary Greetings, Eric - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[BUG] fs/buffer.c:1821 in 2.6.22-rc4-mm2
hi, i got the following BUG while running the syscalls.sh from ltp-full-20070531 on an ext3 partition, it is easily reproducible for me [ 476.338068] [ cut here ] [ 476.338223] kernel BUG at fs/buffer.c:1821! [ 476.338324] invalid opcode: [#1] [ 476.338423] PREEMPT [ 476.338665] Modules linked in: [ 476.338833] CPU:0 [ 476.338836] EIP:0060:[c01a1914]Not tainted VLI [ 476.338840] EFLAGS: 00010202 (2.6.22-rc4-mm2 #1) [ 476.339206] EIP is at __block_prepare_write+0x64/0x410 [ 476.339311] eax: 0001 ebx: c136fbb8 ecx: c07faf28 edx: 0001 [ 476.339417] esi: c1dc9040 edi: c32d2dfc ebp: c3733db8 esp: c3733d50 [ 476.339584] ds: 007b es: 007b fs: gs: 0033 ss: 0068 [ 476.339690] Process vmsplice01 (pid: 7680, ti=c3733000 task=c351ed60 task.ti=c3733000) [ 476.339796] Stack: c3733d70 c0143e76 c1a0eab0 0046 c2509d64 0cd8 c136fbb8 [ 476.340675]c32d2dfc 0296 c02313b6 c1086088 0050 c02313b6 c1dc9040 c2509d50 [ 476.341491]c1dc9054 c3733dc4 c02313e9 c3733dbc c015728d c32d2f0c c136fbb8 [ 476.342371] Call Trace: [ 476.342565] [c01a1d83] block_write_begin+0x83/0xf0 [ 476.342804] [c0207778] ext3_write_begin+0xc8/0x1c0 [ 476.342987] [c01595bf] pagecache_write_begin+0x4f/0x150 [ 476.343243] [c019db3b] pipe_to_file+0x9b/0x170 [ 476.343418] [c019d4b0] __splice_from_pipe+0x70/0x260 [ 476.343654] [c019d6e8] splice_from_pipe+0x48/0x70 [ 476.343828] [c019d9f8] generic_file_splice_write+0x88/0x130 [ 476.344066] [c019d267] do_splice_from+0xb7/0xc0 [ 476.344240] [c019ea51] sys_splice+0x1a1/0x230 [ 476.344474] [c01043be] sysenter_past_esp+0x5f/0x99 [ 476.344656] [e410] 0xe410 [ 476.344882] === [ 476.344984] INFO: lockdep is turned off. [ 476.345084] Code: 00 0f 97 c2 e8 ee 2f 22 00 85 c0 74 04 0f 0b eb fe 31 d2 b8 28 af 7f c0 81 7d 08 00 10 00 00 0f 97 c2 e8 d0 2f 22 00 85 c0 74 04 0f 0b eb fe 8b 55 08 39 55 b0 0f 97 c0 0f b6 d0 b8 0c af 7f c0 [ 476.350365] EIP: [c01a1914] __block_prepare_write+0x64/0x410 SS:ESP 0068:c3733d50 here is the matching .config: # # Automatically generated make config: don't edit # Linux kernel version: 2.6.22-rc4-mm2 # Sun Jun 10 15:27:04 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 # CONFIG_CONTAINER_DEBUG is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_CONTAINER_CPUACCT is not set # CONFIG_RELAY is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set 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_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_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROC_SMAPS=y CONFIG_PROC_CLEAR_REFS=y CONFIG_PROC_PAGEMAP=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set # CONFIG_KMOD is not set CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y # CONFIG_IOSCHED_AS is not set # CONFIG_IOSCHED_DEADLINE is not set CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=cfq # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is
EXT3 fuzzing
hi, after fsfuzz (http://www.securityfocus.com/archive/1/449568/30/0/threaded) was released i decided to give it a spin. So far I got two problematic images: http://www.cobra-basket.de/ext3_ls_prozzy_hog.img.bz2 which makes the kernel use as much cpu as it can get http://www.cobra-basket.de/ext3_memhog.img.bz2 eats all memory it can get I enabled jbd debugging for a while, and the traces looked similar, but made not much sense to me. kmemleak locked my box, so I was not able to get some debugging info from there. To test the images, just mount them, and do an ls on the image. Greetings, Eric -- www.cobra-basket.de -- just my stuff - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
