Re: cred_guard_mutex vs seq_file::lock [was: Re: 3.14.0+/x86: lockdep and mutexes not getting along]
Date
Fri, 11 Apr 2014 15:50:27 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
> Al, David, any bright ideas on how to best fix this?
Have the seq_xxx() code throw an error if current->in_execve is true. I can't think of any circumstance where execve() should be reading anything that uses seq_xxx().