From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: Kirill Korotaev <dev@sw.ru>,
linux-kernel@vger.kernel.org, devel@openvz.org,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: [PATCH] struct file leakage
Date: Mon, 10 Jul 2006 14:16:14 +0400 [thread overview]
Message-ID: <20060710101614.GA834@ms2.inr.ac.ru> (raw)
In-Reply-To: <20060710030526.fdb1ca27.akpm@osdl.org>
Hello!
> I don't understand this. Are you implying that there are other bugs.
Yes. I still see leakage of another objects, most likely fdtables.
Probably, it is an internal bleeding of openvz or it was already fixed
in mainstreem. I still do not know.
Alexey
next prev parent reply other threads:[~2006-07-10 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 9:05 [PATCH] struct file leakage Kirill Korotaev
2006-07-10 10:05 ` Andrew Morton
2006-07-10 10:16 ` Alexey Kuznetsov [this message]
2006-07-11 12:04 ` Trond Myklebust
2006-07-11 23:32 ` Andrew Morton
2006-07-12 0:26 ` Trond Myklebust
2006-07-10 11:56 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2006-07-10 9:05 Kirill Korotaev
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=20060710101614.GA834@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=akpm@osdl.org \
--cc=dev@sw.ru \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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