Re: Out of memory on 3.5 kernels

[Valdis.Kletnieks@vt.edu]

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

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)

I've started bisecting, and gotten this far:

% git bisect log
git bisect start
# bad: [1aa44772a621e8547dc4db41b47c747469fe0ea3] Add linux-next specific files for 20121001
git bisect bad 1aa44772a621e8547dc4db41b47c747469fe0ea3
# good: [fea7a08acb13524b47711625eebea40a0ede69a0] Linux 3.6-rc3
git bisect good fea7a08acb13524b47711625eebea40a0ede69a0
# good: [526c4d73327f56f83da8b8088fd0b3c7be38c7ae] Merge remote-tracking branch 'regulator/for-next'
git bisect good 526c4d73327f56f83da8b8088fd0b3c7be38c7ae
# good: [961d70d88557405c5b7302c7d87752566468f035] Merge remote-tracking branch 'tty/tty-next'
git bisect good 961d70d88557405c5b7302c7d87752566468f035

(That's as far as I've gotten that I trust, the next bisect hits a different problem where
connecting the hard drive and *starting* cryptLuks hangs the machine hard, so I'll
have to finish bisecting that problem first, then return to bisecting this one)

I admit not being sure why you see it on a 3.5 kernel, but I only see it on stuff
that's after 3.6-rc3.

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