All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, John Levon <levon@movementarian.org>
Subject: Re: That xenstored console leak...
Date: Tue, 15 Jan 2008 08:59:49 -0700	[thread overview]
Message-ID: <478CD875.1050303@novell.com> (raw)
In-Reply-To: <C3B276D5.1ACD6%Keir.Fraser@cl.cam.ac.uk>

Keir Fraser wrote:
> On 15/1/08 14:38, "John Levon" <levon@movementarian.org> wrote:
>
>   
>>>> Anyway, seems like we need a simple working fix for 3.1 series, even if
>>>> there's larger surgery done.
>>>>         
>>> I checked your patch in for 3.1, which is probably sufficient there.
>>>       
>> The fix I was referring to was the one for the MAC-lossage issue.
>>     
>
> I'd consider taking Jim's patch to remove the path deletion, and swallow the
> (rather theoretical) xenstore leak across large numbers of device hotplugs.
>   

It's reality, not just theory :-/.  xm network-[attach|detach] does
leak.  block does not as nothing is written to /vm/uuid/device for block
devices.  Not sure about other devices, e.g. vtpm, security labels,
etc.  A quick grep through the sources reveals netif as the only dev
controller invoking _writeVm().

Perhaps we should look at handling network and block devices in a
similar fashion - eliminating the need to write any device info to this
path?

Jim

  reply	other threads:[~2008-01-15 15:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11 17:39 That xenstored console leak John Levon
2008-01-11 19:24 ` Keir Fraser
2008-01-11 19:48 ` Jim Fehlig
2008-01-11 19:57   ` John Levon
2008-01-14 19:27   ` Jim Fehlig
2008-01-14 20:08     ` John Levon
2008-01-14 21:29       ` Keir Fraser
2008-01-14 21:48         ` John Levon
2008-01-14 21:54           ` Keir Fraser
2008-01-14 22:55             ` John Levon
2008-01-14 22:59               ` Daniel P. Berrange
2008-01-15  8:08                 ` Keir Fraser
2008-01-15  8:06               ` Keir Fraser
2008-01-15 13:42                 ` John Levon
2008-01-15 13:54                   ` Keir Fraser
2008-01-15 13:57                   ` Keir Fraser
2008-01-15 13:59                     ` Keir Fraser
2008-01-15 14:31                       ` John Levon
2008-01-15 14:37                         ` Keir Fraser
2008-01-15 14:38                           ` John Levon
2008-01-15 14:42                             ` Keir Fraser
2008-01-15 15:59                               ` Jim Fehlig [this message]
2008-01-15 16:11                                 ` John Levon
2008-01-15 16:28                                   ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2008-01-14 23:49 Jim Fehlig
2008-01-15  8:10 ` Keir Fraser
2008-01-18 23:14 Jim Fehlig
2008-01-18 23:18 ` Keir Fraser
2008-01-18 23:47   ` Jim Fehlig
2008-01-19  8:11     ` Keir Fraser
2008-01-25  2:00       ` Jim Fehlig
2008-01-25  7:44         ` Keir Fraser
     [not found]           ` <479A002E.6010802@novell.com>
2008-01-25 15:41             ` John Levon
2008-01-25 16:21               ` Jim Fehlig

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=478CD875.1050303@novell.com \
    --to=jfehlig@novell.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=levon@movementarian.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.