From: Andrew Morton <akpm@osdl.org>
To: John M Flinchbaugh <glynis@butterfly.hjsoft.com>
Cc: linux-kernel@vger.kernel.org, tomc@compaqnet.fr
Subject: Re: bsd accounting lockups on smp 2.6.x machines
Date: Fri, 9 Apr 2004 03:58:12 -0700 [thread overview]
Message-ID: <20040409035812.70d33081.akpm@osdl.org> (raw)
In-Reply-To: <20040225184724.GA2618@butterfly.hjsoft.com>
John M Flinchbaugh <glynis@butterfly.hjsoft.com> wrote:
>
> i originally reported kernel oopses and locks here against 2.6.1:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=107488761716255&w=2
>
> then another person reported it against 2.6.2:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=107697407107875&w=2
>
> i just saw it happen against 2.6.3, but i couldn't capture an
> oops. it's still out there. does anyone have any leads on what
> causes it? disabling bsd accounting seems to aleviate the
> crashes.
>
> running tomcat's stop script (java processes) triggers it at
> times for me.
Guys, are either of you still able to reproduce this oops in BSD accounting?
If so, would you be able to determine whether this fixes it? Thanks.
diff -puN kernel/acct.c~acct-oops-fix kernel/acct.c
--- 25/kernel/acct.c~acct-oops-fix 2004-04-09 03:52:59.816330248 -0700
+++ 25-akpm/kernel/acct.c 2004-04-09 03:54:08.671862616 -0700
@@ -347,7 +347,10 @@ static void do_acct_process(long exitcod
/* we really need to bite the bullet and change layout */
ac.ac_uid = current->uid;
ac.ac_gid = current->gid;
+
+ read_lock(&tasklist_lock); /* pin current->tty */
ac.ac_tty = current->tty ? old_encode_dev(tty_devnum(current->tty)) : 0;
+ read_unlock(&tasklist_lock);
ac.ac_flag = 0;
if (current->flags & PF_FORKNOEXEC)
_
prev parent reply other threads:[~2004-04-09 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 18:47 John M Flinchbaugh
2004-04-09 10:58 ` Andrew Morton [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=20040409035812.70d33081.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=glynis@butterfly.hjsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomc@compaqnet.fr \
/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®