Re: how does opening a char device set the cdev pointer in the inode?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Robert,

El Tue, Apr 01, 2008 at 08:28:23AM -0400 Robert P. J. Day ha dit:

> On Tue, 1 Apr 2008, Matthias Kaehlcke wrote:
> 
> > they can't arrive at the second test simultaneously cause cdev_lock
> > is used for synchronization.
> >
> > yes, they would set it to the same value, but two calls to
> > list_add(&inode->i_devices, &p->list) would result in
> > inode->i_devices being added twice to p->list.
> 
> other than that issue, matthew, did the rest of my post look
> reasonably accurate in terms of how inode->i_cdev came to be set?

i come to the same conclusion, though i'm probably not the best
reference as i'm still relativly new to the internals of the kernel.

-- 
Matthias Kaehlcke
Linux System Developer
Barcelona

            You can chain me, you can torture me, you can even
          destroy this body, but you will never imprison my mind
                            (Mahatma Gandhi)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux