On Friday, December 14, 2001 09:26:42 AM -0800 Andrew Morton
> Chris Mason wrote:
>> Ok, Johan sent along stack traces, and the deadlock works a little like
>> linux-2.4.16 + reiserfs + quota v2
>> kswapd ->
>> mark_inode_dirty->journal_begin-> wait for trans to end
>> Some process in the transaction is waiting on kswapd to free ram.
> This is unfamiliar. Where does a process block on kswapd in this
> manner? Not __alloc_pages I think.
It kinda blocks on kswapd by default when the process in the transaction
needs to read a block, or allocate one for the commit. Since kswapd is stuck
waiting on the log, eventually a process holding the transaction will try to
allocate something when there are no pages freeable with GFP_NOFS.
It was much worse when we just had GFP_BUFFER before, but the deadlock is
>> So, this will hit any journaled FS that uses quotas and logs inodes under
>> during a write. ext3 doesn't seem to do special things for quota anymore,
>> so it should be affected too.
> mm.. most of the ext3 damage-avoidance hacks are around writepage().
sct talked about how the ext3 data logging code allowed quotas to be
consistent after a crash. Perhaps this was just in 2.2.x...
>> The only fix I see is to make sure kswapd doesn't run shrink_icache, and to
>> have it done via a dedicated daemon instead. Does anyone have a better
> Well, we already need to do something like that to prevent the
> abuse of keventd in there. It appears that somebody had a
> problem with deadlocks doing the inode writeout in kswapd but
> missed the quota problem.
> Is it possible for the quota code to just bale out if PF_MEMALLOC
> is set? To leave the dquot dirty?
We could change prune_icache to skip inodes with dirty quota fields. It
already skips dirty inodes, so this isn't a huge change.
I'll try this, and also add kinoded so we can avoid using keventd. I'm wary
of the affects on the VM if kinoded can't keep up though, so I'd like to keep
the shrink_icache call in kswapd if possible.
Johan, expect this to take at least a week before I suggest installing on
production machines. Things are very intertwined here, and these changes
will probably have side effects that need dealing with.
Turning quotas off will solve the problem in the short term.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:28 EST