Ar Mer, 2006-07-12 am 09:27 +0300, ysgrifennodd Pekka Enberg: > How is this supposed to work? What's stopping a process from > re-opening the file after revoke(2) has been called? File permissions. - 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]>
- Re: tty's use of file_list_lock and file_move
- From: Theodore Tso <[email protected]>
- Re: tty's use of file_list_lock and file_move
- From: "Pekka Enberg" <[email protected]>
- tty's use of file_list_lock and file_move
- Prev by Date: Re: [GIT *] Remove inclusion of obsolete <linux/config.h>
- Next by Date: Re: ipoib lockdep warning
- Previous by thread: Re: tty's use of file_list_lock and file_move
- Next by thread: [PATCH 001/001] /fs/proc/: 'larger than buffer size' memory accesses by clear_user()
- Index(es):
 |