Re: cred_guard_mutex vs seq_file::lock [was: Re: 3.14.0+/x86: lockdep and mutexes not getting along]

[David Howells]

Peter Zijlstra <peterz@xxxxxxxxxxxxx> 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().

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