From: Arnd Bergmann <[email protected]>
Date: Sun, 7 Oct 2007 02:17:08 +0200
> On Saturday 06 October 2007, Jeff Garzik wrote:
> >
> > This always bugged me: dev_ioctl() called dev_ifsioc() either inside
> > read_lock(dev_base_lock) or rtnl_lock(), depending on the ioctl being
> > executed.
> >
> > This change moves the ioctls executed inside dev_base_lock to a new
> > function, dev_ifsioc_locked(). Now the locking context is completely
> > clear to the reader.
> >
> > Signed-off-by: Jeff Garzik <[email protected]>
>
> Great idea!
I think so too, applied, thanks!
-
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/
[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]
