From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, James Bottomley <jejb@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/3 stable 4.9] proc/sysctl: prune stale dentries during unregistering
Date: Mon, 13 Aug 2018 20:38:08 +0300 [thread overview]
Message-ID: <20180813173807.GA5467@rapoport-lnx> (raw)
In-Reply-To: <20180813171312.GA24864@kroah.com>
On Mon, Aug 13, 2018 at 07:13:12PM +0200, Greg KH wrote:
> On Mon, Aug 13, 2018 at 01:04:24PM +0300, Mike Rapoport wrote:
> > On Mon, Aug 13, 2018 at 11:23:25AM +0200, Greg KH wrote:
> > > On Mon, Aug 13, 2018 at 12:08:15PM +0300, Mike Rapoport wrote:
> > > > Hi,
> > > >
> > > > These patches fix a memory leak in per-cpu areas in v4.9.y
> > > >
> > > > The following command sequence
> > > >
> > > > while :; do
> > > > c=$(docker create busybox)
> > > > docker start $c
> > > > docker stop $c
> > > > docker rm $c
> > > > done
> > > >
> > > > causes the number of pcpu_get_vm_area entries in /proc/vmallocinfo to grow.
> > > >
> > > > The commit d6cffbbe9a7e ("proc/sysctl: prune stale dentries during
> > > > unregistering") fixes the issue and the commits ace0c791e6c3 ("proc/sysctl:
> > > > Don't grab i_lock under sysctl_lock.") and 2fd1d2c4ceb2 ("proc: Fix
> > > > proc_sys_prune_dcache to hold a sb reference") are the follow-up fixups.
> > > >
> > > > I've also checked v4.4 and the issue does not appear there.
> > > >
> > > > Eric W. Biederman (2):
> > > > proc/sysctl: Don't grab i_lock under sysctl_lock.
> > > > proc: Fix proc_sys_prune_dcache to hold a sb reference
> > > >
> > > > Konstantin Khlebnikov (1):
> > > > proc/sysctl: prune stale dentries during unregistering
> > >
> > > What is the git commit ids of these patches that are in Linus's tree? I
> > > need those to be able to apply this.
> >
> > d6cffbbe9a7e ("proc/sysctl: prune stale dentries during unregistering")
> > ace0c791e6c3 ("proc/sysctl: Don't grab i_lock under sysctl_lock.")
> > 2fd1d2c4ceb2 ("proc: Fix proc_sys_prune_dcache to hold a sb reference")
>
> Thanks, now queued up. Any reason why you did not sign off on the
> backports?
They've applied cleanly, I didn't really work in the backporting, only on
the bisecting :)
> greg k-h
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2018-08-13 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 9:08 [PATCH 0/3 stable 4.9] proc/sysctl: prune stale dentries during unregistering Mike Rapoport
2018-08-13 9:08 ` [PATCH 1/3] " Mike Rapoport
2018-08-13 9:08 ` [PATCH 2/3] proc/sysctl: Don't grab i_lock under sysctl_lock Mike Rapoport
2018-08-13 9:08 ` [PATCH 3/3] proc: Fix proc_sys_prune_dcache to hold a sb reference Mike Rapoport
2018-08-13 9:23 ` [PATCH 0/3 stable 4.9] proc/sysctl: prune stale dentries during unregistering Greg KH
2018-08-13 9:24 ` Greg KH
2018-08-13 10:04 ` Mike Rapoport
2018-08-13 17:13 ` Greg KH
2018-08-13 17:38 ` Mike Rapoport [this message]
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=20180813173807.GA5467@rapoport-lnx \
--to=rppt@linux.vnet.ibm.com \
--cc=greg@kroah.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=stable@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.