Re: 2.6.2-rc3-mm1

From: Helge Hafting (helgehaf_at_aitel.hist.no)
Date: 02/03/04

  • Next message: Ingo Molnar: "Re: New v. v. experimental HOTPLUG CPU megapatch."
    Date:	Tue, 03 Feb 2004 11:16:08 +0100
    To: Andrew Morton <akpm@osdl.org>
    
    

    Andrew Morton wrote:
    > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc3/2.6.2-rc3-mm1/
    >
    >
    > - There is a debug patch in here which detects when someone calls
    > i_size_write() without holding the inode's i_sem. It generates a warning
    > and a stack backtrace. We know that XFS generates such a trace. It will
    > turn itself off after the first ten warnings. Please don't report the XFS
    > case.
    >
    Ok, here's an ext2 case, from dmesg:

    md: running: <hdb1><hda1>
    raid1: raid set md0 active with 2 out of 2 mirrors
    md: ... autorun DONE.
    VFS: Mounted root (ext2 filesystem) readonly.
    Freeing unused kernel memory: 168k freed
    Adding 1999864k swap on /dev/hdb2. Priority:-1 extents:1
    Disabled Privacy Extensions on device c042ca80(lo)
    i_size_write() called without i_sem
    Call Trace:
     [<c012e66c>] i_size_write_check+0x3a/0x4d
     [<c0145444>] generic_commit_write+0x4e/0x70
     [<c0169886>] ext2_commit_chunk+0x28/0x61
     [<c016aa1d>] ext2_make_empty+0x158/0x1e0
     [<c016d3d5>] ext2_mkdir+0xa1/0xff
     [<c016d334>] ext2_mkdir+0x0/0xff
     [<c014d592>] vfs_mkdir+0x60/0x83
     [<c014d639>] sys_mkdir+0x84/0xbf
     [<c036133f>] syscall_call+0x7/0xb

    i_size_write() called without i_sem
    Call Trace:
     [<c012e66c>] i_size_write_check+0x3a/0x4d
     [<c0145444>] generic_commit_write+0x4e/0x70
     [<c0169886>] ext2_commit_chunk+0x28/0x61
     [<c016aa1d>] ext2_make_empty+0x158/0x1e0
     [<c016d3d5>] ext2_mkdir+0xa1/0xff
     [<c016d334>] ext2_mkdir+0x0/0xff
     [<c014d592>] vfs_mkdir+0x60/0x83
     [<c014d639>] sys_mkdir+0x84/0xbf
     [<c036133f>] syscall_call+0x7/0xb

    i_size_write() called without i_sem
    Call Trace:
     [<c012e66c>] i_size_write_check+0x3a/0x4d
     [<c0145444>] generic_commit_write+0x4e/0x70
     [<c0169886>] ext2_commit_chunk+0x28/0x61
     [<c016aa1d>] ext2_make_empty+0x158/0x1e0
     [<c016d3d5>] ext2_mkdir+0xa1/0xff
     [<c016d334>] ext2_mkdir+0x0/0xff
     [<c014d592>] vfs_mkdir+0x60/0x83
     [<c014d639>] sys_mkdir+0x84/0xbf
     [<c036133f>] syscall_call+0x7/0xb

    eth0: no IPv6 routers present
    atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
    atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.

    2.6.2-rc3-mm1 compiled with mregparm3

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


  • Next message: Ingo Molnar: "Re: New v. v. experimental HOTPLUG CPU megapatch."

    Relevant Pages

    • 2.6.2-mm1+XFS
      ... trace related to XFS in my logs. ... Ending clean XFS mount for filesystem: ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.19-rc6 : Spontaneous reboots, stack overflows - seems to implicate xfs, scsi, networ
      ... >> I'll try to extract a copy of each unique trace that involves xfs, ... > one instance of each unique stack overflow + trace that I've got. ... It is hard to know who to blame, there is no information about stack ... bool "Use 4Kb for kernel stacks instead of 8Kb" ...
      (Linux-Kernel)
    • Re: 2.6.22-rc3 hibernate(?) fails totally - regression (xfs on raid6)
      ... clean boot, unmounting the xfs fs: ... git bisect good 0a3fd051c7036ef71b58863f8e5da7c3dabd9d3f ... Call Trace: ...
      (Linux-Kernel)
    • Re: raid5 crash
      ... > I doubt very much that this would happen with ext3. ... > about xfs, but I doubt it would happen their either. ... Call Trace: ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.4.23-pre9 ide+XFree+ptrace=Complete hang
      ... there is any way to get the Xserver running without ioplbut using ... ioperm instead - I know that the io bitmap is only 0x400 ports, ... Any ideas on how to trace this down? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)