tty's use of file_list_lock and file_move

Since you want a new subject can you explain tty's use of file_lock to
me? Is there some non-obvious global coordination happening here or is
it work breaking down the big kernel lock that never got finished?

--
Jon Smirl
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: tty's use of file_list_lock and file_move
  - From: Alan Cox <[email protected]>

Prev by Date: Re: lockdep input layer warnings.
Next by Date: Re: Follow up? LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
Previous by thread: [patch] i386: handle_BUG(): don't print garbage if debug info unavailable
Next by thread: Re: tty's use of file_list_lock and file_move
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]