Bug#931111: linux-image-4.9.0-9: Memory "leak" caused by CGroup as used by pam_systemd

Hello, Am 24.07.19 um 16:41 schrieb Roman Gushchin: > On Wed, Jul 24, 2019 at 09:12:50AM +0200, Philipp Hahn wrote: >> Am 24.07.19 um 00:03 schrieb Ben Hutchings: ... >>> I would say this is a kernel bug. I think it's the same problem that >>> this patch series is trying to solve: >>>

Bug#931111: linux-image-4.9.0-9: Memory "leak" caused by CGroup as used by pam_systemd

On Wed, Jul 24, 2019 at 09:12:50AM +0200, Philipp Hahn wrote: > Hello Ben, > > Am 24.07.19 um 00:03 schrieb Ben Hutchings: > > On Tue, 2019-07-23 at 15:56 +0200, Philipp Hahn wrote: > > [...] > >> - when the job / session terminates, the directory is deleted by > >> pam_systemd. > >> > >> - but

Bug#931111: linux-image-4.9.0-9: Memory "leak" caused by CGroup as used by pam_systemd

Hello Ben, Am 24.07.19 um 00:03 schrieb Ben Hutchings: > On Tue, 2019-07-23 at 15:56 +0200, Philipp Hahn wrote: > [...] >> - when the job / session terminates, the directory is deleted by >> pam_systemd. >> >> - but the Linux kernel still uses the CGroup to track kernel internal >> memory (SLAB

Bug#931111: linux-image-4.9.0-9: Memory "leak" caused by CGroup as used by pam_systemd

On Tue, 2019-07-23 at 15:56 +0200, Philipp Hahn wrote: [...] > - when the job / session terminates, the directory is deleted by > pam_systemd. > > - but the Linux kernel still uses the CGroup to track kernel internal > memory (SLAB objects, pending cache pages, ...?) > > - inside the kernel the

Bug#931111: linux-image-4.9.0-9: Memory "leak" caused by CGroup as used by pam_systemd

Hi, I analyzed the issue and the problem seems to be CGroup related: - we're using 'pam_systemd' in "/etc/pam.d/common-session" - each cron-job / login then creates a new CGroup below "/sys/fs/cgroup/systemd/user.slice/" while that job / session is running - when the job / session terminates,