From: Sean Hunter <sean@dev.sportingbet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: /proc/meminfo swap counter wraparound in 2.2
Date: Wed, 12 Sep 2001 11:31:26 +0100 [thread overview]
Message-ID: <20010912113126.Q6126@dev.sportingbet.com> (raw)
In-Reply-To: <20010912105151.L6126@dev.sportingbet.com> <E15h6vz-0004Fb-00@the-village.bc.nu> <20010912111229.P6126@dev.sportingbet.com>
In-Reply-To: <20010912111229.P6126@dev.sportingbet.com>; from sean@dev.sportingbet.com on Wed, Sep 12, 2001 at 11:12:29AM +0100
On Wed, Sep 12, 2001 at 11:12:29AM +0100, Sean Hunter wrote:
> On Wed, Sep 12, 2001 at 11:07:55AM +0100, Alan Cox wrote:
> > > I would be amazed if this bug were not also in the main 2.2.x tree. Is a fix
> > > likely or even possible in 2.2 ?
> >
> > No fix is planned for 2.2
> >
>
> OK, thanks. I'm a little reluctant to move this box to 2.4 yet (before Monday
> we had almost a year's uptime out of it- frequent reboots are frowned upon),
> but looking at the 2.4 source, the relevant bits of fs/proc/array.c and
> include/linux/kernel.h look exactly the same, so the problem could be there as
> well.
>
> Am I being dumb?
Yes, of course I am. Having now Actually Tried It Instead Of Just Talking
Bollocks[tm], I can confirm that large amounts of swap space seem to work just
fine in 2.4.
Sorry for wasting people's time.
Sean
prev parent reply other threads:[~2001-09-12 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 9:51 /proc/meminfo swap counter wraparound in 2.2 Sean Hunter
2001-09-12 10:07 ` Alan Cox
2001-09-12 10:12 ` Sean Hunter
2001-09-12 10:31 ` Sean Hunter [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=20010912113126.Q6126@dev.sportingbet.com \
--to=sean@dev.sportingbet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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