Re: tty's use of file_list_lock and file_move

Ar Llu, 2006-07-10 am 14:09 -0400, ysgrifennodd Jon Smirl:
> > We hold the ->files->file_lock because we have to walk other processes
> > file tables in a safe fashion in SAK. That one is fairly clear.
> 
> What if do_SAK did something like this?
> 
> copy the tty struct to new_tty
> NULL out the file list in new_tty
> insert new_tty into the array tracking tty minors so that open will
> find the new one

SAK isn't locking against the tty layer ,its locking against the VFS
when it does htis


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

---

• References:
  • tty's use of file_list_lock and file_move
    • From: "Jon Smirl" <[email protected]>
  • Re: tty's use of file_list_lock and file_move
    • From: Alan Cox <[email protected]>
  • Re: tty's use of file_list_lock and file_move
    • From: "Jon Smirl" <[email protected]>
  • Re: tty's use of file_list_lock and file_move
    • From: Alan Cox <[email protected]>
  • Re: tty's use of file_list_lock and file_move
    • From: "Jon Smirl" <[email protected]>

• Prev by Date: Re: [BUG] APM resume breakage from 2.6.18-rc1 clocksource changes
• Next by Date: Re: tty's use of file_list_lock and file_move
• Previous by thread: Re: tty's use of file_list_lock and file_move
• 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]