From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Kieran <kieran@ihateaol.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: proc_pid_stat crashes in 2.6.2 (was 2.6.0-test11: Crash in ps axH)
Date: Thu, 19 Feb 2004 19:34:16 +0100 [thread overview]
Message-ID: <20040219183416.GA12962@vana.vc.cvut.cz> (raw)
In-Reply-To: <403500DA.3060906@ihateaol.co.uk>
On Thu, Feb 19, 2004 at 06:30:50PM +0000, Kieran wrote:
> >Hi,
> > I already reported this crash twice on 2.6.0-test11, and now I
> >reproduced it on something more fresh - on 2.6.2-bk-something like it
> >was actual on Feb 4. It is really annoying, as any user can do 'ps axH'
> >and crash system after some uptime :-( Crash is identical to one
> >I got with 2.6.0-test11, so it looks like that I'll have to go back
> >to 2.4.x on publicly accessible machines. After about 14 days uptime.
> >
> > I've got no replies to previous reports.
> > Thanks,
> > Petr Vandrovec
> > vandrove@vc.cvut.cz
>
> what version of procps?
Not that it should matter, as walking through /proc/* could do same,
but... 3.1.15-3. I have no idea what procps were installed at the
beginning of February or in the December. Until crash 'ps ax' does not
cause problem. Only 'axH', which descends to /task/ subdirectories,
crashes.
usermap:~# dpkg -l procps
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==========================-==========================-====================================================================
ii procps 3.1.15-3 The /proc file system utilities
usermap:~#
Petr Vandrovec
next prev parent reply other threads:[~2004-02-19 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 18:23 Petr Vandrovec
2004-02-19 18:30 ` Kieran
2004-02-19 18:34 ` Petr Vandrovec [this message]
2004-02-19 18:48 ` Petr Vandrovec
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=20040219183416.GA12962@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=kieran@ihateaol.co.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
all inboxes | Powered by JetHome®