On Fri, Sep 23, 2005 at 10:56:53PM +0530, Dipankar Sarma wrote:
>
> Well, the main reason is that if that code is somehow copied
> by to a lock-free critical section, it could cause problems.
> If you dereference ->fdt multiple times in a lock-free
> section, you could see two different pointers due to
> a concurrent update.
thanks for the explanation. This raises a lot of other questions. What
if max_fds is updated by RCU right after obtaining it...
--
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: max_fd
- From: Dipankar Sarma <dipankar@in.ibm.com>
- References:
- max_fd
- From: Pablo Fernandez <pablo.ferlop@gmail.com>
- Re: max_fd
- From: Dipankar Sarma <dipankar@in.ibm.com>
- Re: max_fd
- From: Frank van Maarseveen <frankvm@frankvm.com>
- Re: max_fd
- From: Dipankar Sarma <dipankar@in.ibm.com>
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]