All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Weissenbacher <mw@dermichi.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Kernel 2.6.30: Memory/XFS leak, OOM killer kills many processes
Date: Fri, 12 Jun 2009 11:57:03 +0200	[thread overview]
Message-ID: <4A32266F.8080607@dermichi.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0906120420080.26259@p34.internal.lan>

Hi!
> 
> So just goto line ~6086 and add the kmem_free(out); above the return error.
> 
> Status:
> This patch fixes the problem, thanks!
> 
Applied here too & fixes the problem. Wow, the fix was provided in <3 hours, kudos to open source.

Michael

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Michael Weissenbacher <mw@dermichi.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Felix Blyakher <felixb@sgi.com>,
	Eric Sandeen <sandeen@sandeen.net>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Kernel 2.6.30: Memory/XFS leak, OOM killer kills many processes
Date: Fri, 12 Jun 2009 11:57:03 +0200	[thread overview]
Message-ID: <4A32266F.8080607@dermichi.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0906120420080.26259@p34.internal.lan>

Hi!
> 
> So just goto line ~6086 and add the kmem_free(out); above the return error.
> 
> Status:
> This patch fixes the problem, thanks!
> 
Applied here too & fixes the problem. Wow, the fix was provided in <3 hours, kudos to open source.

Michael

  reply	other threads:[~2009-06-12  9:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 16:15 Kernel 2.6.30: Memory/XFS leak, OOM killer kills many processes Justin Piszcz
2009-06-11 16:15 ` Justin Piszcz
2009-06-11 17:00 ` Justin Piszcz
2009-06-11 17:00   ` Justin Piszcz
2009-06-11 17:31   ` Eric Sandeen
2009-06-11 17:31     ` Eric Sandeen
2009-06-11 19:02     ` Felix Blyakher
2009-06-11 19:02       ` Felix Blyakher
2009-06-11 22:02       ` Mike Dresser
2009-06-11 22:02         ` Mike Dresser
2009-06-11 21:35     ` Felix Blyakher
2009-06-11 21:35       ` Felix Blyakher
2009-06-12  8:37       ` Justin Piszcz
2009-06-12  8:37         ` Justin Piszcz
2009-06-12  9:57         ` Michael Weissenbacher [this message]
2009-06-12  9:57           ` Michael Weissenbacher
2009-06-12 15:54         ` Felix Blyakher
2009-06-12 15:54           ` Felix Blyakher
2009-06-11 18:49 ` markus reichelt

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=4A32266F.8080607@dermichi.com \
    --to=mw@dermichi.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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.