On Sat, 20 Oct 2012 08:42:33 -0400 Paul Moore <paul@xxxxxxxxxxxxxx> wrote: > Thanks for the problem report. I'm not going to be in a position to start > looking into this until late Sunday, but hopefully it will be a quick fix. > > Two quick questions (my apologies, I'm not able to dig through your logs > right now): do you see this leak on kernels < 3.5.0, and are you using any > labeled IPsec connections? > As I understand, labelled connections are only used in SELinux and SMACK LSM, which are not enabled (in Kconfig, i.e. not built) in any of the kernels I use. The only LSM I have enabled (and actually use on 2/4 of these machines) is AppArmor, and though I think it doesn't attach any labels to network connections yet (there's a "Wishlist" bug at https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/796588, but I can't seem to find an existing implementation). I believe it has started with 3.5.0, according to all available logs I have. I'm afraid laziness and other tasks have prevented me from looking into and reporting the issue back then, but memory graph trends start at the exact time of reboot into 3.5.0 kernels, and before that, there're no such trends for slab memory usage. I've been able to ignore and work around the problem for months now, so I don't think there's any rush at all ;) But that said, currently I've started git bisect process between v3.5 and v3.4 tags, so hopefully I'll get good-enough results of it before you'll get to it (probably in a few hours to a few days). Also, I've found that switching to "slab" allocator from "slub" doesn't help the problem at all, so I guess something doesn't get freed in the code indeed, though I hasn't been able to find anything relevant in the logs for the sources where secpath_put and secpath_dup are used, and decided to try bisect. -- Mike Kazantsev // fraggod.net
Attachment:
signature.asc
Description: PGP signature