From: Avi Kivity <avi@argo.co.il>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: local denial-of-service with file leases
Date: Fri, 11 Nov 2005 12:05:38 +0200 [thread overview]
Message-ID: <43746CF2.5000501@argo.co.il> (raw)
In-Reply-To: <20051111084554.GZ7991@shell0.pdx.osdl.net>
Chris Wright wrote:
>* Avi Kivity (avi@argo.co.il) wrote:
>
>
>>the following program will oom a the 2.6.14.1 kernel, running as an
>>ordinary user:
>>
>>
>
>I don't have a good mechanism for testing leases, but this should fix
>the leak. Mind testing?
>
>
>
the test program of course passes, but now samba hangs when reading a
file (mount -t cifs from the same machine). 2.6.14.1 reads the file but
leaks memory.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2005-11-11 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 17:00 local denial-of-service with file leases Avi Kivity
2005-11-11 8:45 ` Chris Wright
2005-11-11 10:05 ` Avi Kivity [this message]
2005-11-11 11:14 ` Avi Kivity
2005-11-11 14:21 ` Trond Myklebust
2005-11-11 18:35 ` Chris Wright
2005-11-11 19:25 ` Trond Myklebust
2005-11-12 1:20 ` Chris Wright
2005-11-13 9:05 ` Avi Kivity
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=43746CF2.5000501@argo.co.il \
--to=avi@argo.co.il \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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