From: Florian Weimer <Florian.Weimer@RUS.Uni-Stuttgart.DE>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.2.13] memory leak in NFS if a sever goes away?
Date: 01 Aug 2001 12:32:19 +0200 [thread overview]
Message-ID: <tgy9p4jcjw.fsf@mercury.rus.uni-stuttgart.de> (raw)
In-Reply-To: <tgsnfdkrsu.fsf@mercury.rus.uni-stuttgart.de> <20010731232456.A13258@emma1.emma.line.org>
In-Reply-To: <20010731232456.A13258@emma1.emma.line.org> (Matthias Andree's message of "Tue, 31 Jul 2001 23:24:56 +0200")
Matthias Andree <matthias.andree@stud.uni-dortmund.de> writes:
> > Are there some known issues with 2.2.13, for example, a memory leak in
> > the NFS code which is triggered in this specific situation?
>
> There are known security threats in 2.2.x which have been fixed in
> 2.2.16, and there have been VM fixes in a later version, and further
> minor but numerable security fixes in 2.2.19.
The system has already been installed from scratch, using a more
recent kernel version. I agree that the kind of information I'm
looking for is not crucial for running a current Linux kernel, but we
were specifically asked to explain what has happened to the machine
(and we do have satisfactory explanations for other strange things
which were obsvered---no it wasn't hacked ;-), but this problem still
remains a bit mysterious. I just wanted to make sure that the problem
described in my first posting is not a once well-known issue with
2.2.13 or other 2.2.x kernels, and that I didn't miss an obvious
explanation.
--
Florian Weimer Florian.Weimer@RUS.Uni-Stuttgart.DE
University of Stuttgart http://cert.uni-stuttgart.de/
RUS-CERT +49-711-685-5973/fax +49-711-685-5898
prev parent reply other threads:[~2001-08-01 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 16:05 Florian Weimer
2001-07-31 21:24 ` Matthias Andree
2001-08-01 10:32 ` Florian Weimer [this message]
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=tgy9p4jcjw.fsf@mercury.rus.uni-stuttgart.de \
--to=florian.weimer@rus.uni-stuttgart.de \
--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
all inboxes | Powered by JetHome®