Re: [PATCH] tty: add lockdep annotations
From: Linus Torvalds
Date: Sat Jun 02 2012 - 18:25:48 EST
On Sat, Jun 2, 2012 at 1:19 PM, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
>
> Yep. Been that way 8)
>
> tty_driver_remove_tty is called from tty_shutdown is called from the
> final tty_kref_put can be called from IRQ context.
Hmm. Ok. Looking at it, the ".shutdown" and ".remove" functions are
all very limited, so I suspect we could just make the rule be that the
install/lookup functions are serialized against each other by the
pty_mutex (true today), and then we just add a small spinlock for the
actual driver array insert/lookup.
So my patch could probably be munged to do something like that.
But since I want to close the merge window and release -rc1 today, it
does feel too late to start mucking with fundamental locking things.
So reverting is likely the right thing to do.
Can somebody double-check the attached revert commit? Did I miss some
commit that depended on the tty locking changes?
Eric, does this make things work for you again? When/if we get the
locking sorted out for the tty install/lookup/remove, we can revert
this revert and do the locking fixes on top of that.
Alan, please double-check my revert. I've done an allmodconfig build
with it, and I've looked at the patch and grepped that I didn't miss
any 'tty_[un]lock()' cases, but that's the limit of my
sanity-checking. I did check that this revert means that the main tty
files are now back in the same exact state they were before that
"tty_lock: Localise the lock" commit. I left the per-ldisc waitqueue
change in there, though, that one seemed independent.
Linus
Attachment:
tty-locking-revert.patch
Description: Binary data