mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Anton Petrusevich <casus@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: threads & /proc
Date: Fri, 23 Nov 2001 22:19:17 -0800	[thread overview]
Message-ID: <3BFF3BE5.EECBB5D0@zip.com.au> (raw)
In-Reply-To: <20011123233857.A25084@casus.tx>

Anton Petrusevich wrote:
> 
> Hi Guys,
> 
> Well, I'm a bit surprised that nobody asked it yet. Do we have sound
> thread support? I am able to put my linux-2.4.15-pre{1,7} --
> definitely, and if I remember right, 2.4.14-pre{7,8} too in some strange
> state, when any program like top, killall or ps that wanna get some
> information from /proc (even midnight commander if you are trying to
> look at state of any process) blocks indefinitely. It goes to unclean
> shutdown, for example. kill doesn block, but do nothing. (I tried to
> kill processes from ls /proc list). And I see it only after several
> [unsuccessful] runs of my multithreaded program. Well, I can't say
> it's a correctly written program, I am still looking for bugs there.
> I don't have 100% way to get into this state, but I suspect some locking
> issues with /proc.

I've seen this once, on a semi-production machine which, unfortunately,
wasn't set up for diagnostic work.  Uniprocessor.

If you can send out some code which demonstrates the bug then
that will be invaluable - it will be fixed quickly.

-

  reply	other threads:[~2001-11-24  6:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24  5:38 Anton Petrusevich
2001-11-24  6:19 ` Andrew Morton [this message]
2001-11-24  8:11 ` Peter Zaitsev
2001-11-26  5:46   ` FORT David
2001-11-28  0:18 Luke
2001-11-28 10:08 ` Luigi Genoni

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=3BFF3BE5.EECBB5D0@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=casus@mail.ru \
    --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®