Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263146AbTEVTIX (ORCPT ); Thu, 22 May 2003 15:08:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263150AbTEVTIX (ORCPT ); Thu, 22 May 2003 15:08:23 -0400 Received: from franka.aracnet.com ([216.99.193.44]:34980 "EHLO franka.aracnet.com") by vger.kernel.org with ESMTP id S263146AbTEVTIR (ORCPT ); Thu, 22 May 2003 15:08:17 -0400 Date: Thu, 22 May 2003 12:21:14 -0700 From: "Martin J. Bligh" To: linux-kernel Subject: [Bug 739] New: Null pointer dereference in ext3_test_allocatable Message-ID: <7240000.1053631274@[10.10.2.4]> X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4025 Lines: 103 Summary: Null pointer dereference in ext3_test_allocatable Kernel Version: 2.5.69-mm8 Status: NEW Severity: normal Owner: akpm@digeo.com Submitter: plars@austin.ibm.com Distribution: RH7.3 Hardware Environment: 8-way PIII-700, 16 GB ram Software Environment: anticipatory scheduler, ext3, preempt enabled Problem Description: While I was trying to reproduce bug 738, I got this but I believe it is sufficiently different enough to call it a new bug. Apologies in advance if I'm wrong on that. I was also able to produce this one earlier today when I was compiling LTP but was unsuccessful upon trying it again. I didn't have the serial console setup during the LTP compile when I produced this bug the first time so I missed the output that time, but I recognize the Null pointer and the EIP from before. Unable to handle kernel NULL pointer dereference at virtual address 00000010 printing eip: c0197db3 *pde = 35b80001 Oops: 0000 [#1] CPU: 3 EIP: 0060:[] Not tainted VLI EFLAGS: 00010206 EIP is at ext3_test_allocatable+0x23/0x40 eax: 00000000 ebx: f6a9e000 ecx: 00002c76 edx: f6628688 esi: 00002c76 edi: 00002c60 ebp: 00000000 esp: f6b11a2c ds: 007b es: 007b ss: 0068 Process ftest07 (pid: 1354, threadinfo=f6b10000 task=f63a3920) Stack: c0197f9f 00002c76 f6628688 00000000 00001000 f6a9e000 00008000 ffffffff f7c6351c f6628688 c01980d6 ffffffff f6628688 00008000 00000000 c0160744 f7c5c6dc 001c0000 00001000 00000037 00000038 f7c6351c f6b11ac8 c019848d Call Trace: [] find_next_usable_block+0x1cf/0x2c0 [] ext3_try_to_allocate+0x46/0x190 [] __bread+0x14/0x30 [] ext3_new_block+0x26d/0x610 [] __wake_up+0x66/0xb0 [] ext3_alloc_block+0x1d/0x30 [] ext3_alloc_branch+0x45/0x280 [] bh_lru_install+0xca/0xf0 [] ext3_get_block_handle+0x20f/0x2f0 [] alloc_buffer_head+0x13/0x60 [] create_buffers+0x57/0xb0 [] ext3_get_block+0x60/0x70 [] __block_prepare_write+0x140/0x3e0 [] __up_wakeup+0x8/0xc [] block_prepare_write+0x20/0x40 [] ext3_get_block+0x0/0x70 [] ext3_prepare_write+0x42/0xe0 [] ext3_get_block+0x0/0x70 [] generic_file_aio_write_nolock+0x66e/0xac0 [] unlock_page+0xa/0x50 [] file_read_actor+0x64/0xd0 [] file_read_actor+0x71/0xd0 [] do_generic_mapping_read+0xf5/0x4f0 [] update_atime+0x6d/0xc0 [] __generic_file_aio_read+0x1b5/0x1e0 [] generic_file_write_nolock+0x99/0xc0 [] __block_write_full_page+0x284/0x3f0 [] autoremove_wake_function+0x0/0x40 [] autoremove_wake_function+0x0/0x40 [] mpage_writepages+0x234/0x3d0 [] blkdev_writepage+0x0/0x20 [] check_poison_obj+0x39/0x190 [] kmalloc+0xfa/0x1c0 [] generic_file_writev+0x40/0x60 [] do_readv_writev+0x1c0/0x270 [] do_sync_write+0x0/0xe0 [] generic_file_llseek+0x2d/0xd0 [] generic_file_llseek+0x0/0xd0 [] vfs_writev+0x47/0x50 [] sys_writev+0x2f/0x50 [] syscall_call+0x7/0xb Code: 00 8d bc 27 00 00 00 00 8b 54 24 08 8b 4c 24 04 8b 42 18 0f a3 08 19 c0 85 c0 74 03 31 c0 c3 8b 02 a9 00 04 00 00 74 0a 8b 42 24 <8b> 40 10 85 c0 75 06 b8 01 00 00 00 c3 0f a3 08 19 d2 31 c0 85 Steps to reproduce: from a current CVS of LTP (today is 5/22/2003): run ftest07 in one session while waiting for that to complete (it takes a while) I ran these: aio01 -n100000 aio01 -c10 -n10000 Both completed successfully but when ftest07 finished it had the output above. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/