Re: File Descriptor

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

 



On Tue, 2004-11-30 at 15:40 -0800, Usman S. Ansari wrote:
> In this particular situation, I would like to do some cleanup, without
> too much overhead.
> 
> What I mean, there could be a situation in which we will tell our
> customer that "this senario can result in unpredictable results".
> 
> Therefore I do not want to go through (nor I have time) to make a
> list, maintain a list, etc, but if such a list is already maintained
> by the kernel, than I can quickly go and do cleanup

I doubt that there is any list (Greg KH - and lots of other people
around - knowns way much more of the kernel than /me sp listen to them
if in doubt).
Especially since it is quite unclear what you mean with "my
descriptors".
- All file descriptors of your driver (excluding dup(), dup2() and
  dup-through-fork())
- All file descriptors of one device of your driver (excluding dup(),
  dup2() and dup-through-fork())

And BTW your driver has no chance to get to know if user-space dup()s,
dup2()s or fork()s (and thus also dup()s a file descriptor).

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services




--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           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