Re: sleeping function called from invalid context at block/cfq-iosched.c (Was: Re: 2.6.21-mm1)



On Mon, May 07, 2007 at 10:38:24PM -0700, Jeremy Fitzhardinge wrote:
Andrew Morton wrote:
On Mon, 07 May 2007 21:31:06 -0700 Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

I've found that XFS+lvm+4k stacks is completely unusable with current
kernels. I get hangs/oopes after ~10mins of work.


Sounds like this is new behaviour?

I wonder why. Same compiler version?

I've only recently started using xfs, so I couldn't say if its new
behaviour. I did notice that it took a week or so for problems to set
in; my theory is that as the filesystem got a bit aged, its
datastructures got a bit more complex, and cause the kernel code to use
more stack. But that's just a guess.

The worst case stack usage through XFS occurs when it has to read
metadata blocks in the writeback path when doing an allocation
transaction. This happens when walking the freespace btrees looking
for an extent matching the allocation requirements. As the fileystem
fills up, these btrees will grow and you are more likely not to have
a block inthe btree cached in memory.

So yes, this is a possible reason you hadn't seen any problems early
on.

FWIW, there's also been recent reports of both ext3 and reiser on
LVM blowing 4k stacks, so if you use LVM it probably advisable to
go back to 8k stacks....

Cheers,

Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: 2.6.19-rc6 : Spontaneous reboots, stack overflows - seems to implicate xfs, scsi, networ
    ... >>identify areas where XFS could use less stack space by reducing/avoid large ... I've got one that prevents gcc from inlining single use functions in XFS ... If you want/need more traces then I've got ~2.1G ...
    (Linux-Kernel)
  • Re: Panic with XFS on RHEL5 (2.6.18-8.1.8.el5)
    ... Does anyone have any hits/tips for using XFS on Red Hat? ... function in the call stack suggested to me that you might have an ext3 ... The situation was earlier on was iso9660 on loop on xfs on lvm on cciss. ... None of the loop devices would have been mounted. ...
    (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)
  • 2.0.x kernels and stack leak under high interrupt load
    ... I'm working on a problem I'm having in 2.0 kernels (embedded product, ... The backtrace is full of nothing but ret_from_sys_call and ... the ret_from_sys_call cannot complete) eventually eats up the stack. ... The high interrupt load in this case is caused by a constant high load ...
    (Linux-Kernel)
  • Re: Panic with XFS on RHEL5 (2.6.18-8.1.8.el5)
    ... I've got a box running RHEL5 and haven't been impressed by ext3 ... so often the kernel panics as below. ... Does anyone have any hits/tips for using XFS on Red Hat? ... function in the call stack suggested to me that you might have an ext3 ...
    (Linux-Kernel)