public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Nyberg <alexn@dsv.su.se>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Bryce Harrington <bryce@osdl.org>, Chris Wright <chrisw@osdl.org>,
	dev@osdl.org, linux-kernel@vger.kernel.org,
	stp-devel@lists.sourceforge.net
Subject: Re: Kernel 2.6.11-rc1/2 goes Postal on LTP
Date: Tue, 25 Jan 2005 20:12:01 +0100	[thread overview]
Message-ID: <1106680321.705.52.camel@boxen> (raw)
In-Reply-To: <41F46B32.9070904@osdl.org>

> Similar for me, easy to reproduce (3 times today).
> Here's a kernel messages log, with 32 processes killed,
> mostly hotplug, but also bash (2x), runltp, & some daemons.
> 
> I could not login and do anything else, but I could/did
> SysRq-T, P, M, S, U, B to reboot.  These are also in the log.
> 
> log:
> http://developer.osdl.org/rddunlap/oom/oom_kill.txt
> 
> config:
> http://developer.osdl.org/rddunlap/oom/config-2611rc2
> 
> on P4-UP, 1 GB RAM.
> 

I saw this aswell. Appears to be the pipe leak cause it doesn't go nuts
with the patch at the bottom from Linus.


> 
> Would indicate that the new pipe code is leaking.

Duh. It's the pipe merging.

		Linus

----
--- 1.40/fs/pipe.c	2005-01-15 12:01:16 -08:00
+++ edited/fs/pipe.c	2005-01-24 14:35:09 -08:00
@@ -630,13 +630,13 @@
 	struct pipe_inode_info *info = inode->i_pipe;
 
 	inode->i_pipe = NULL;
-	if (info->tmp_page)
-		__free_page(info->tmp_page);
 	for (i = 0; i < PIPE_BUFFERS; i++) {
 		struct pipe_buffer *buf = info->bufs + i;
 		if (buf->ops)
 			buf->ops->release(info, buf);
 	}
+	if (info->tmp_page)
+		__free_page(info->tmp_page);
 	kfree(info);
 }
 



  reply	other threads:[~2005-01-25 19:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.58.0410011536060.2403@ppc970.osdl.org>
2005-01-19  0:19 ` LTP Results for 2.6.x and 2.4.x Bryce Harrington
2005-01-21 19:27   ` Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x) Bryce Harrington
2005-01-21 23:35     ` Andrew Morton
2005-01-21 23:33       ` [Dev] " Chris Wright
2005-01-22  1:08         ` Bryce Harrington
2005-01-22  3:11           ` [LTP] " Bryce Harrington
2005-01-22  5:05             ` Chris Wright
2005-01-22 20:14               ` Kernel 2.6.11-rc1/2 goes Postal on LTP Bryce Harrington
2005-01-23 22:20                 ` Randy.Dunlap
2005-01-24  3:27                 ` Randy.Dunlap
2005-01-25 19:12                   ` Alexander Nyberg [this message]
2005-01-25 18:28                     ` Randy.Dunlap
2005-01-21 23:41       ` Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x) William Lee Irwin III

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=1106680321.705.52.camel@boxen \
    --to=alexn@dsv.su.se \
    --cc=bryce@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=dev@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=stp-devel@lists.sourceforge.net \
    /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