All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: James Cloos <cloos@jhcloos.com>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: Likely mem leak in 3.7
Date: Fri, 16 Nov 2012 11:17:07 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1211161115001.2788@chino.kir.corp.google.com> (raw)
In-Reply-To: <m3r4nuwipl.fsf@carbon.jhcloos.org>

On Thu, 15 Nov 2012, James Cloos wrote:

> The kernel does not log anything relevant to this.
> 

Can you do the following as root:

	dmesg -c > /dev/null
	echo m > /proc/sysrq-trigger
	dmesg > foo

and send foo inline in your reply?

> Slabinfo gives some odd output.  It seems to think there are negative
> quantities of some slabs:
> 
> Name                   Objects Objsize    Space Slabs/Part/Cpu  O/S O %Fr %Ef Flg
> :at-0000016               5632      16    90.1K 18446744073709551363/0/275  256 0   0 100 *a
> :t-0000048                3386      48   249.8K 18446744073709551558/22/119   85 0  36  65 *
> :t-0000120                1022     120   167.9K 18446744073709551604/14/53   34 0  34  73 *
> blkdev_requests            182     376   122.8K 18446744073709551604/7/27   21 1  46  55 
> ext4_io_end                348    1128   393.2K 18446744073709551588/0/40   29 3   0  99 a
> 

Can you send the output of

	zgrep CONFIG_SL[AU]B /proc/config.gz
	cat /proc/slabinfo

  reply	other threads:[~2012-11-16 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 23:26 Likely mem leak in 3.7 James Cloos
2012-11-16 19:17 ` David Rientjes [this message]
2012-11-18  0:29   ` James Cloos
2012-12-01 22:48     ` James Cloos

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=alpine.DEB.2.00.1211161115001.2788@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=cloos@jhcloos.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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 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.