linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Dan Eaton <Dan.Eaton@rlx.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] hppfs file descriptor leak?
Date: Mon, 03 May 2004 22:21:02 -0400	[thread overview]
Message-ID: <200405040221.i442L2ml026618@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 03 May 2004 11:25:12 CDT." <1083601512.6946.6.camel@dan>

Dan.Eaton@rlx.com said:
> It seems that each access to /proc entries that I am spoofing from the
> host results in an open file that never gets closed.  I am looking at
> it via gdb but any insight that anyone has would be greatly
> appreciated.

First I've heard of it, but I'm not too surprised.  The thing to do to
track it down is see what file descriptors are being lost by looking at
/proc/<uml-pid>/fd.  It should be pretty obvious.

I'll take a look at it when I get a chance.

				Jeff



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-05-04  1:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 16:25 [uml-devel] hppfs file descriptor leak? Dan Eaton
2004-05-04  2:21 ` Jeff Dike [this message]
2004-05-04 16:01   ` Richard Potter
2004-05-04 20:39     ` Jeff Dike
2005-09-05 20:35 ` Blaisorblade
2005-09-08 17:53   ` Antoine Martin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200405040221.i442L2ml026618@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=Dan.Eaton@rlx.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox