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]

 



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?

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

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