[BUG] 2.6.24.4 kernel bug while running ftest03 - Kernel

This is a discussion on [BUG] 2.6.24.4 kernel bug while running ftest03 - Kernel ; Hi, The kernel panic's, while running the LTP ftest03 on the 2.6.24.4 kernel compiled with the gcov patches from LTP. ( http://ltp.cvs.sourceforge.net/ltp/u...ch?view=markup ) BUG: unable to handle kernel paging request at virtual address f8000004 printing eip: c01c2836 *pdpt = 0000000000004001 ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: [BUG] 2.6.24.4 kernel bug while running ftest03

  1. [BUG] 2.6.24.4 kernel bug while running ftest03

    Hi,

    The kernel panic's, while running the LTP ftest03 on the 2.6.24.4 kernel
    compiled with the gcov patches from LTP.
    (http://ltp.cvs.sourceforge.net/ltp/u...ch?view=markup)

    BUG: unable to handle kernel paging request at virtual address f8000004
    printing eip: c01c2836 *pdpt = 0000000000004001 *pde = 0000000000000000
    Oops: 0000 [#1] SMP

    Modules linked in: hidp rfcomm l2cap bluetooth dm_multipath nvram via686a hwmon i2c_viapro pcspkr mptsas scsi_transport_sas floppy tg3 parport_pc ac battery button dm_mirror dm_mod joydev sunrpc i2c_dev i2c_core autofs4 lp parport ipv6 md5 sg mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ehci_hcd ohci_hcd uhci_hcdPid: 24160, comm: ftest03 Not tainted (2.6.24.4-gcov-autokern1 #1)

    EIP: 0060:[] EFLAGS: 00010246 CPU: 1
    EIP is at iov_iter_advance+0xe9/0x155
    EAX: 00000000 EBX: f3457d98 ECX: 00000080 EDX: 00000000
    ESI: 00000000 EDI: f8000000 EBP: f33f6d30 ESP: f3457d24
    DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
    Process ftest03 (pid: 24160, ti=f3457000 task=f6544590 task.ti=f3457000)
    Stack: 00000800 0006b800 00000000 c01c5e79 0006b800 00000000 00000800 00000800
    c7209030 c015cdea f3457e8c f7fb9180 f33f6d30 c07b1600 f33f6c68 00000000
    00000800 00000800 00000000 c07b1600 00000000 0000006b f3457da8 c02f11cd
    Call Trace:
    [] generic_file_buffered_write+0x29f/0xc05
    [] current_fs_time+0x4e/0x6f
    [] ext3_readpages+0x0/0x35
    [] ext3_readpages+0x0/0x35
    [] __do_page_cache_readahead+0x268/0x386
    [] current_fs_time+0x4e/0x6f
    [] __generic_file_aio_write_nolock+0x7b8/0x852
    [] generic_file_aio_write+0x8d/0x162
    [] generic_file_aio_read+0x292/0x31a
    [] ext3_file_write+0x32/0x17c
    [] do_sync_readv_writev+0xcf/0x152
    [] wait_on_page_writeback_range+0x153/0x1e7
    [] autoremove_wake_function+0x0/0x5f
    [] copy_from_user+0xb1/0x135
    [] rw_copy_check_uvector+0xd2/0x19f
    [] do_readv_writev+0x152/0x328
    [] ext3_file_write+0x0/0x17c
    [] _spin_unlock+0x13/0x22
    [] audit_syscall_entry+0x2eb/0x323
    [] vfs_writev+0x8c/0x9e
    [] sys_writev+0x8b/0x1a5
    [] syscall_call+0x7/0xb
    =======================
    Code: c0 00 29 c8 01 ce 89 43 0c 39 77 04 75 13 83 c7 08 83 05 98 63 a6 c0 01 83 15 9c 63 a6 c0 00 31 f6 29 ca 85 d2 0f 85 78 ff ff ff <83> 7f 04 00 75 29 83 05 a0 63 a6 c0 01 83 15 a4 63 a6 c0 00 83 EIP: [] iov_iter_advance+0xe9/0x155 SS:ESP 0068:f3457d24---[ end trace af3ae442124c3d18 ]---
    --
    Thanks & Regards,
    Kamalesh Babulal,
    Linux Technology Center,
    IBM, ISTL.
    --
    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/

  2. Re: [BUG] 2.6.24.4 kernel bug while running ftest03

    Hello,

    > The kernel panic's, while running the LTP ftest03 on the 2.6.24.4 kernel
    > compiled with the gcov patches from LTP.
    > (http://ltp.cvs.sourceforge.net/ltp/u...ch?view=markup)

    Are you able to reproduce the problem without this patch? The patch is
    nontrivial...

    > BUG: unable to handle kernel paging request at virtual address f8000004

    The address is a bit strange. Looks like we have advanced iov beyond
    the area we have allocated. Can you send me disassembly of the function
    iov_iter_advance() of your kernel? Thanks.

    > printing eip: c01c2836 *pdpt = 0000000000004001 *pde = 0000000000000000
    > Oops: 0000 [#1] SMP
    >
    > Modules linked in: hidp rfcomm l2cap bluetooth dm_multipath nvram via686a hwmon i2c_viapro pcspkr mptsas scsi_transport_sas floppy tg3 parport_pc ac battery button dm_mirror dm_mod joydev sunrpc i2c_dev i2c_core autofs4 lp parport ipv6 md5 sg mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ehci_hcd ohci_hcd uhci_hcdPid: 24160, comm: ftest03 Not tainted (2.6.24.4-gcov-autokern1 #1)
    >
    > EIP: 0060:[] EFLAGS: 00010246 CPU: 1
    > EIP is at iov_iter_advance+0xe9/0x155
    > EAX: 00000000 EBX: f3457d98 ECX: 00000080 EDX: 00000000
    > ESI: 00000000 EDI: f8000000 EBP: f33f6d30 ESP: f3457d24
    > DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
    > Process ftest03 (pid: 24160, ti=f3457000 task=f6544590 task.ti=f3457000)
    > Stack: 00000800 0006b800 00000000 c01c5e79 0006b800 00000000 00000800 00000800
    > c7209030 c015cdea f3457e8c f7fb9180 f33f6d30 c07b1600 f33f6c68 00000000
    > 00000800 00000800 00000000 c07b1600 00000000 0000006b f3457da8 c02f11cd
    > Call Trace:
    > [] generic_file_buffered_write+0x29f/0xc05
    > [] current_fs_time+0x4e/0x6f
    > [] ext3_readpages+0x0/0x35
    > [] ext3_readpages+0x0/0x35
    > [] __do_page_cache_readahead+0x268/0x386
    > [] current_fs_time+0x4e/0x6f
    > [] __generic_file_aio_write_nolock+0x7b8/0x852
    > [] generic_file_aio_write+0x8d/0x162
    > [] generic_file_aio_read+0x292/0x31a
    > [] ext3_file_write+0x32/0x17c
    > [] do_sync_readv_writev+0xcf/0x152
    > [] wait_on_page_writeback_range+0x153/0x1e7
    > [] autoremove_wake_function+0x0/0x5f
    > [] copy_from_user+0xb1/0x135
    > [] rw_copy_check_uvector+0xd2/0x19f
    > [] do_readv_writev+0x152/0x328
    > [] ext3_file_write+0x0/0x17c
    > [] _spin_unlock+0x13/0x22
    > [] audit_syscall_entry+0x2eb/0x323
    > [] vfs_writev+0x8c/0x9e
    > [] sys_writev+0x8b/0x1a5
    > [] syscall_call+0x7/0xb
    > =======================
    > Code: c0 00 29 c8 01 ce 89 43 0c 39 77 04 75 13 83 c7 08 83 05 98 63 a6 c0 01 83 15 9c 63 a6 c0 00 31 f6 29 ca 85 d2 0f 85 78 ff ff ff <83> 7f 04 00 75 29 83 05 a0 63 a6 c0 01 83 15 a4 63 a6 c0 00 83 EIP: [] iov_iter_advance+0xe9/0x155 SS:ESP 0068:f3457d24---[ end trace af3ae442124c3d18 ]---


    Honza
    --
    Jan Kara
    SuSE CR Labs
    --
    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/

  3. Re: [BUG] 2.6.24.4 kernel bug while running ftest03

    Hello,

    I've just found that Nick has been recently fixing this function,
    Nick?
    Honza

    > > The kernel panic's, while running the LTP ftest03 on the 2.6.24.4 kernel
    > > compiled with the gcov patches from LTP.
    > > (http://ltp.cvs.sourceforge.net/ltp/u...ch?view=markup)

    > Are you able to reproduce the problem without this patch? The patch is
    > nontrivial...
    >
    > > BUG: unable to handle kernel paging request at virtual address f8000004

    > The address is a bit strange. Looks like we have advanced iov beyond
    > the area we have allocated. Can you send me disassembly of the function
    > iov_iter_advance() of your kernel? Thanks.
    >
    > > printing eip: c01c2836 *pdpt = 0000000000004001 *pde = 0000000000000000
    > > Oops: 0000 [#1] SMP
    > >
    > > Modules linked in: hidp rfcomm l2cap bluetooth dm_multipath nvram via686a hwmon i2c_viapro pcspkr mptsas scsi_transport_sas floppy tg3 parport_pc ac battery button dm_mirror dm_mod joydev sunrpc i2c_dev i2c_core autofs4 lp parport ipv6 md5 sg mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ehci_hcd ohci_hcd uhci_hcdPid: 24160, comm: ftest03 Not tainted (2.6.24.4-gcov-autokern1 #1)
    > >
    > > EIP: 0060:[] EFLAGS: 00010246 CPU: 1
    > > EIP is at iov_iter_advance+0xe9/0x155
    > > EAX: 00000000 EBX: f3457d98 ECX: 00000080 EDX: 00000000
    > > ESI: 00000000 EDI: f8000000 EBP: f33f6d30 ESP: f3457d24
    > > DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
    > > Process ftest03 (pid: 24160, ti=f3457000 task=f6544590 task.ti=f3457000)
    > > Stack: 00000800 0006b800 00000000 c01c5e79 0006b800 00000000 00000800 00000800
    > > c7209030 c015cdea f3457e8c f7fb9180 f33f6d30 c07b1600 f33f6c68 00000000
    > > 00000800 00000800 00000000 c07b1600 00000000 0000006b f3457da8 c02f11cd
    > > Call Trace:
    > > [] generic_file_buffered_write+0x29f/0xc05
    > > [] current_fs_time+0x4e/0x6f
    > > [] ext3_readpages+0x0/0x35
    > > [] ext3_readpages+0x0/0x35
    > > [] __do_page_cache_readahead+0x268/0x386
    > > [] current_fs_time+0x4e/0x6f
    > > [] __generic_file_aio_write_nolock+0x7b8/0x852
    > > [] generic_file_aio_write+0x8d/0x162
    > > [] generic_file_aio_read+0x292/0x31a
    > > [] ext3_file_write+0x32/0x17c
    > > [] do_sync_readv_writev+0xcf/0x152
    > > [] wait_on_page_writeback_range+0x153/0x1e7
    > > [] autoremove_wake_function+0x0/0x5f
    > > [] copy_from_user+0xb1/0x135
    > > [] rw_copy_check_uvector+0xd2/0x19f
    > > [] do_readv_writev+0x152/0x328
    > > [] ext3_file_write+0x0/0x17c
    > > [] _spin_unlock+0x13/0x22
    > > [] audit_syscall_entry+0x2eb/0x323
    > > [] vfs_writev+0x8c/0x9e
    > > [] sys_writev+0x8b/0x1a5
    > > [] syscall_call+0x7/0xb
    > > =======================
    > > Code: c0 00 29 c8 01 ce 89 43 0c 39 77 04 75 13 83 c7 08 83 05 98 63 a6 c0 01 83 15 9c 63 a6 c0 00 31 f6 29 ca 85 d2 0f 85 78 ff ff ff <83> 7f 04 00 75 29 83 05 a0 63 a6 c0 01 83 15 a4 63 a6 c0 00 83 EIP: [] iov_iter_advance+0xe9/0x155 SS:ESP 0068:f3457d24---[ end trace af3ae442124c3d18 ]---

    >
    > Honza
    > --
    > Jan Kara
    > SuSE CR Labs
    > --
    > 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/

    --
    Jan Kara
    SuSE CR Labs
    --
    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/

  4. Re: [BUG] 2.6.24.4 kernel bug while running ftest03

    On Thu, Apr 03, 2008 at 02:53:44PM +0200, Jan Kara wrote:
    > Hello,
    >
    > I've just found that Nick has been recently fixing this function,
    > Nick?


    Hmm, yes it looks like an earlier oops but that should be fixed in
    2.6.24.4... I can't see a way it could advance off the end of the
    iovec now. Sigh.

    Is the problem easy to reproduce (preferably without the gov patch
    but even with the patch...).

    I couldn't reproduce the bug with ftest03.

    >
    > Honza
    >
    > > > The kernel panic's, while running the LTP ftest03 on the 2.6.24.4 kernel
    > > > compiled with the gcov patches from LTP.
    > > > (http://ltp.cvs.sourceforge.net/ltp/u...ch?view=markup)

    > > Are you able to reproduce the problem without this patch? The patch is
    > > nontrivial...
    > >
    > > > BUG: unable to handle kernel paging request at virtual address f8000004

    > > The address is a bit strange. Looks like we have advanced iov beyond
    > > the area we have allocated. Can you send me disassembly of the function
    > > iov_iter_advance() of your kernel? Thanks.
    > >
    > > > printing eip: c01c2836 *pdpt = 0000000000004001 *pde = 0000000000000000
    > > > Oops: 0000 [#1] SMP
    > > >
    > > > Modules linked in: hidp rfcomm l2cap bluetooth dm_multipath nvram via686a hwmon i2c_viapro pcspkr mptsas scsi_transport_sas floppy tg3 parport_pc ac battery button dm_mirror dm_mod joydev sunrpc i2c_dev i2c_core autofs4 lp parport ipv6 md5 sg mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ehci_hcd ohci_hcd uhci_hcdPid: 24160, comm: ftest03 Not tainted (2.6.24.4-gcov-autokern1 #1)
    > > >
    > > > EIP: 0060:[] EFLAGS: 00010246 CPU: 1
    > > > EIP is at iov_iter_advance+0xe9/0x155
    > > > EAX: 00000000 EBX: f3457d98 ECX: 00000080 EDX: 00000000
    > > > ESI: 00000000 EDI: f8000000 EBP: f33f6d30 ESP: f3457d24
    > > > DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
    > > > Process ftest03 (pid: 24160, ti=f3457000 task=f6544590 task.ti=f3457000)
    > > > Stack: 00000800 0006b800 00000000 c01c5e79 0006b800 00000000 00000800 00000800
    > > > c7209030 c015cdea f3457e8c f7fb9180 f33f6d30 c07b1600 f33f6c68 00000000
    > > > 00000800 00000800 00000000 c07b1600 00000000 0000006b f3457da8 c02f11cd
    > > > Call Trace:
    > > > [] generic_file_buffered_write+0x29f/0xc05
    > > > [] current_fs_time+0x4e/0x6f
    > > > [] ext3_readpages+0x0/0x35
    > > > [] ext3_readpages+0x0/0x35
    > > > [] __do_page_cache_readahead+0x268/0x386
    > > > [] current_fs_time+0x4e/0x6f
    > > > [] __generic_file_aio_write_nolock+0x7b8/0x852
    > > > [] generic_file_aio_write+0x8d/0x162
    > > > [] generic_file_aio_read+0x292/0x31a
    > > > [] ext3_file_write+0x32/0x17c
    > > > [] do_sync_readv_writev+0xcf/0x152
    > > > [] wait_on_page_writeback_range+0x153/0x1e7
    > > > [] autoremove_wake_function+0x0/0x5f
    > > > [] copy_from_user+0xb1/0x135
    > > > [] rw_copy_check_uvector+0xd2/0x19f
    > > > [] do_readv_writev+0x152/0x328
    > > > [] ext3_file_write+0x0/0x17c
    > > > [] _spin_unlock+0x13/0x22
    > > > [] audit_syscall_entry+0x2eb/0x323
    > > > [] vfs_writev+0x8c/0x9e
    > > > [] sys_writev+0x8b/0x1a5
    > > > [] syscall_call+0x7/0xb
    > > > =======================
    > > > Code: c0 00 29 c8 01 ce 89 43 0c 39 77 04 75 13 83 c7 08 83 05 98 63 a6 c0 01 83 15 9c 63 a6 c0 00 31 f6 29 ca 85 d2 0f 85 78 ff ff ff <83> 7f 04 00 75 29 83 05 a0 63 a6 c0 01 83 15 a4 63 a6 c0 00 83 EIP: [] iov_iter_advance+0xe9/0x155 SS:ESP 0068:f3457d24---[ end trace af3ae442124c3d18 ]---

    --
    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/

  5. Re: [BUG] 2.6.24.4 kernel bug while running ftest03

    Nick Piggin wrote:
    > On Thu, Apr 03, 2008 at 02:53:44PM +0200, Jan Kara wrote:
    >> Hello,
    >>
    >> I've just found that Nick has been recently fixing this function,
    >> Nick?

    >
    > Hmm, yes it looks like an earlier oops but that should be fixed in
    > 2.6.24.4... I can't see a way it could advance off the end of the
    > iovec now. Sigh.
    >
    > Is the problem easy to reproduce (preferably without the gov patch
    > but even with the patch...).
    >
    > I couldn't reproduce the bug with ftest03.


    I tried without the gcov patch and I am not able to reproduce it,
    >
    >>
    >> Honza
    >>
    >>>> The kernel panic's, while running the LTP ftest03 on the 2.6.24.4 kernel
    >>>> compiled with the gcov patches from LTP.
    >>>> (http://ltp.cvs.sourceforge.net/ltp/u...ch?view=markup)
    >>> Are you able to reproduce the problem without this patch? The patch is
    >>> nontrivial...
    >>>
    >>>> BUG: unable to handle kernel paging request at virtual address f8000004
    >>> The address is a bit strange. Looks like we have advanced iov beyond
    >>> the area we have allocated. Can you send me disassembly of the function
    >>> iov_iter_advance() of your kernel? Thanks.


    Sorry, I do not have the kernel, i will try reproducing the get it.
    >>>
    >>>> printing eip: c01c2836 *pdpt = 0000000000004001 *pde = 0000000000000000
    >>>> Oops: 0000 [#1] SMP
    >>>>
    >>>> Modules linked in: hidp rfcomm l2cap bluetooth dm_multipath nvram via686a hwmon i2c_viapro pcspkr mptsas scsi_transport_sas floppy tg3 parport_pc ac battery button dm_mirror dm_mod joydev sunrpc i2c_dev i2c_core autofs4 lp parport ipv6 md5 sg mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ehci_hcd ohci_hcd uhci_hcdPid: 24160, comm: ftest03 Not tainted (2.6.24.4-gcov-autokern1 #1)
    >>>>
    >>>> EIP: 0060:[] EFLAGS: 00010246 CPU: 1
    >>>> EIP is at iov_iter_advance+0xe9/0x155
    >>>> EAX: 00000000 EBX: f3457d98 ECX: 00000080 EDX: 00000000
    >>>> ESI: 00000000 EDI: f8000000 EBP: f33f6d30 ESP: f3457d24
    >>>> DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
    >>>> Process ftest03 (pid: 24160, ti=f3457000 task=f6544590 task.ti=f3457000)
    >>>> Stack: 00000800 0006b800 00000000 c01c5e79 0006b800 00000000 00000800 00000800
    >>>> c7209030 c015cdea f3457e8c f7fb9180 f33f6d30 c07b1600 f33f6c68 00000000
    >>>> 00000800 00000800 00000000 c07b1600 00000000 0000006b f3457da8 c02f11cd
    >>>> Call Trace:
    >>>> [] generic_file_buffered_write+0x29f/0xc05
    >>>> [] current_fs_time+0x4e/0x6f
    >>>> [] ext3_readpages+0x0/0x35
    >>>> [] ext3_readpages+0x0/0x35
    >>>> [] __do_page_cache_readahead+0x268/0x386
    >>>> [] current_fs_time+0x4e/0x6f
    >>>> [] __generic_file_aio_write_nolock+0x7b8/0x852
    >>>> [] generic_file_aio_write+0x8d/0x162
    >>>> [] generic_file_aio_read+0x292/0x31a
    >>>> [] ext3_file_write+0x32/0x17c
    >>>> [] do_sync_readv_writev+0xcf/0x152
    >>>> [] wait_on_page_writeback_range+0x153/0x1e7
    >>>> [] autoremove_wake_function+0x0/0x5f
    >>>> [] copy_from_user+0xb1/0x135
    >>>> [] rw_copy_check_uvector+0xd2/0x19f
    >>>> [] do_readv_writev+0x152/0x328
    >>>> [] ext3_file_write+0x0/0x17c
    >>>> [] _spin_unlock+0x13/0x22
    >>>> [] audit_syscall_entry+0x2eb/0x323
    >>>> [] vfs_writev+0x8c/0x9e
    >>>> [] sys_writev+0x8b/0x1a5
    >>>> [] syscall_call+0x7/0xb
    >>>> =======================
    >>>> Code: c0 00 29 c8 01 ce 89 43 0c 39 77 04 75 13 83 c7 08 83 05 98 63 a6 c0 01 83 15 9c 63 a6 c0 00 31 f6 29 ca 85 d2 0f 85 78 ff ff ff <83> 7f 04 00 75 29 83 05 a0 63 a6 c0 01 83 15 a4 63 a6 c0 00 83 EIP: [] iov_iter_advance+0xe9/0x155 SS:ESP 0068:f3457d24---[ end trace af3ae442124c3d18 ]---



    --
    Thanks & Regards,
    Kamalesh Babulal,
    Linux Technology Center,
    IBM, ISTL.
    --
    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/

+ Reply to Thread