linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel20120920@schottelius.org>
To: Valdis.Kletnieks@vt.edu
Cc: Nico Schottelius <nico-kernel20120920@schottelius.org>,
	David Rientjes <rientjes@google.com>,
	Arend van Spriel <arend@broadcom.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Dave Kleikamp <shaggy@kernel.org>,
	jfs-discussion@lists.sourceforge.net
Subject: Re: Out of memory on 3.5 kernels
Date: Fri, 5 Oct 2012 19:51:39 +0200	[thread overview]
Message-ID: <20121005175139.GC831@schottelius.org> (raw)
In-Reply-To: <22962.1349452084@turing-police.cc.vt.edu>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

Hey Valdis,

Valdis.Kletnieks@vt.edu [Fri, Oct 05, 2012 at 11:48:04AM -0400]:
> On Wed, 03 Oct 2012 23:23:11 +0200, Nico Schottelius said:
> 
> > does anyone of you have a clue so far what may be causing the huge
> > slab usage?
> >
> > I've just found an interesting detail: umounting and cryptsetup
> > luksClosing frees up the used memory (not sure which one was freeing
> > up)
> 
> For what it's worth, I'm seeing a similar problem in linux-next on my laptop -
> trying to run a backup to an external hard drive that has a LUKS partition on
> it will OOM. (For some reason having the external LUKS partition is much more
> problematic than the LVM-on-LUKS on the internal drive)

Indeed, I also have the internal drive encrypted with LUKS, also jfs
on it, but the problem only occurs on the external drive.

Is there the possibility that the JFS on the external drive got into a
state that may caus JFS to behave unexpected? If this is true, it would
explain why it happens only with the external drive and also accross
kernel versions.

But "good" to hear I am not the only one affected anymore.

Cheers,

Nico


-- 
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-10-05 17:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 13:52 Out of memory on 3.5 kernels Arend van Spriel
2012-09-21 19:49 ` Nico Schottelius
2012-09-21 21:02   ` Fwd: " Arend van Spriel
2012-09-24 22:43   ` David Rientjes
2012-09-25 15:07     ` Dave Kleikamp
2012-09-26  6:03       ` Nico Schottelius
2012-09-26  6:06     ` Nico Schottelius
2012-09-26  8:57       ` Nico Schottelius
2012-09-27  5:52         ` Nico Schottelius
2012-10-03 21:23           ` Nico Schottelius
2012-10-05 15:48             ` Valdis.Kletnieks
2012-10-05 17:51               ` Nico Schottelius [this message]
2012-10-30 10:35                 ` Nico Schottelius
2012-11-01 18:04                   ` [Jfs-discussion] " Tino Reichardt
2012-11-21 22:37                   ` Dave Kleikamp
2012-11-27 15:56                     ` [Jfs-discussion] " Dave Kleikamp
2012-11-27 16:11                       ` Nico Schottelius

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=20121005175139.GC831@schottelius.org \
    --to=nico-kernel20120920@schottelius.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=arend@broadcom.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=shaggy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).