lkml.org 
[lkml]   [2013]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 3.11.4: kernel BUG at fs/buffer.c:1268
On Thu, Oct 17, 2013 at 05:11:43PM -0400, George Spelvin wrote:
> Al Viro wrote:
> > Note that do_group_exit() is preceded by
> > spin_unlock_irq(&sighand->siglock);
> > so no matter what happened in callers, irq is enabled. I'd suggest sticking
> > such BUG_ON() into __fput() and trying to reproduce that crap...
>
> Well, it happened again (error appended). Can you please clarify what you mean
> by "such BUG_ON()"; I'm having a hard time following the RCU code and determining
> all the situations under which __fput() might be called.

__fput() can be called via task_work_run() or via schedule_work(). That's
all. And it certainly should never be called with interrupts disabled.
So stick BUG_ON(irqs_disabled()) in it (WARN_ON() might be better, but
not by much).

There are two ways these traces could've happened:
* exit_task_work() called by do_exit() with irqs disabled.
Definitely buggy (and would do really nasty things to several functions
called by do_exit() before that one). If such BUG_ON() triggers in
__fput(), this is what happens and the next step will be sticking
several BUG_ON(irqs_disabled()) in do_exit() - something like
BUG_ON(irqs_disabled());
exit_sem(tsk);
BUG_ON(irqs_disabled());
exit_shm(tsk);
BUG_ON(irqs_disabled());
exit_files(tsk);
BUG_ON(irqs_disabled());
exit_fs(tsk);
BUG_ON(irqs_disabled());
exit_task_namespaces(tsk);
BUG_ON(irqs_disabled());
exit_task_work(tsk);
and checking which of those triggers; that'll tell us who has disabled it
and forgot to enable.
* __fput() is called with irqs enabled, but somewhere on the
way into ext4 (dput -> iput -> evict inode -> free blocks, now that
unlinked file got closed -> ...) we manage to disable irqs and forget
to enable them.


\
 
 \ /
  Last update: 2013-10-18 00:21    [W:0.064 / U:0.992 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site