From: Keith Owens <kaos@ocs.com.au>
To: Marc-Christian Petersen <m.c.p@kernel.linux-systeme.com>
Cc: linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com
Subject: Re: [patch 2.4.28-rc1] Avoid oops in proc_delete_inode
Date: Fri, 05 Nov 2004 07:35:05 +1100 [thread overview]
Message-ID: <11726.1099600505@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 04 Nov 2004 16:29:17 BST." <200411041629.17443@WOLK>
On Thu, 4 Nov 2004 16:29:17 +0100,
Marc-Christian Petersen <m.c.p@kernel.linux-systeme.com> wrote:
>On Thursday 04 November 2004 03:35, Keith Owens wrote:
>
>Marcelo,
>
>I just saw you applied this to bk. Cool, but please apply a right version ;)
>
>> Under heavy load, vmstat, top and other programs that access /proc can
>> oops. PROC_INODE_PROPER(inode) is sometimes false for pid entries
>> (usually zombies), but inode->u.generic_ip is not NULL.
>>
>> Backport a fix by AL Viro from 2.5.7-pre2 to 2.4.28-rc1.
>>
>> Signed-off-by: Keith Owens <kaos@sgi.com>
>>
>> Index: 2.4.28-rc1/fs/proc/base.c
>> ===================================================================
>> --- 2.4.28-rc1.orig/fs/proc/base.c 2004-08-08 10:10:49.000000000 +1000
>> +++ 2.4.28-rc1/fs/proc/base.c 2004-11-04 13:25:16.402602459 +1100
>> @@ -780,6 +780,7 @@ out:
>> return inode;
>>
>> out_unlock:
>> + node->u.generic_ip = NULL;
>
>has to be:
>
> + inode->u.generic_ip = NULL;
>
>> iput(inode);
>> return NULL;
>> }
Oops, copied the old patch into the mail. Where did I put that brown
paper bag?
prev parent reply other threads:[~2004-11-04 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 2:35 [patch 2.4.28-rc1] Avoid oops in proc_delete_inode Keith Owens
2004-11-04 15:29 ` Marc-Christian Petersen
2004-11-04 17:31 ` Marcelo Tosatti
2004-11-04 20:35 ` Keith Owens [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=11726.1099600505@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@kernel.linux-systeme.com \
--cc=marcelo.tosatti@cyclades.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.