From: Tejun Heo <tj@kernel.org> To: Johannes Weiner <hannes@cmpxchg.org> Cc: Will Deacon <will.deacon@arm.com>, "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>, Vladimir Davydov <vdavydov@parallels.com>, "linux-mm@kvack.org" <linux-mm@kvack.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "mhocko@suse.cz" <mhocko@suse.cz>, "akpm@linux-foundation.org" <akpm@linux-foundation.org> Subject: Re: [Regression] 3.19-rc3 : memcg: Hang in mount memcg Date: Thu, 22 Jan 2015 09:34:54 -0500 [thread overview] Message-ID: <20150122143454.GA4507@htj.dyndns.org> (raw) In-Reply-To: <20150122134550.GA13876@phnom.home.cmpxchg.org> Hello, On Thu, Jan 22, 2015 at 08:45:50AM -0500, Johannes Weiner wrote: > diff --git a/kernel/cgroup.c b/kernel/cgroup.c > index bb263d0caab3..9a09308c8066 100644 > --- a/kernel/cgroup.c > +++ b/kernel/cgroup.c > @@ -1819,8 +1819,11 @@ static struct dentry *cgroup_mount(struct file_system_type *fs_type, > goto out_unlock; > } > > - if (root->flags ^ opts.flags) > - pr_warn("new mount options do not match the existing superblock, will be ignored\n"); > + if (root->flags ^ opts.flags) { > + pr_warn("new mount options do not match the existing superblock\n"); > + ret = -EBUSY; > + goto out_unlock; > + } Do we really need the above chunk? > @@ -1909,7 +1912,7 @@ static void cgroup_kill_sb(struct super_block *sb) > * > * And don't kill the default root. > */ > - if (css_has_online_children(&root->cgrp.self) || > + if (!list_empty(&root->cgrp.self.children) || > root == &cgrp_dfl_root) > cgroup_put(&root->cgrp); I tried to do something a bit more advanced so that eventual async release of dying children, if they happen, can also release the hierarchy but I don't think it really matters unless we can forcefully drain. So, shouldn't just the above part be enough? Thanks. -- tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org> To: Johannes Weiner <hannes@cmpxchg.org> Cc: Will Deacon <will.deacon@arm.com>, "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>, Vladimir Davydov <vdavydov@parallels.com>, "linux-mm@kvack.org" <linux-mm@kvack.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "mhocko@suse.cz" <mhocko@suse.cz>, "akpm@linux-foundation.org" <akpm@linux-foundation.org> Subject: Re: [Regression] 3.19-rc3 : memcg: Hang in mount memcg Date: Thu, 22 Jan 2015 09:34:54 -0500 [thread overview] Message-ID: <20150122143454.GA4507@htj.dyndns.org> (raw) In-Reply-To: <20150122134550.GA13876@phnom.home.cmpxchg.org> Hello, On Thu, Jan 22, 2015 at 08:45:50AM -0500, Johannes Weiner wrote: > diff --git a/kernel/cgroup.c b/kernel/cgroup.c > index bb263d0caab3..9a09308c8066 100644 > --- a/kernel/cgroup.c > +++ b/kernel/cgroup.c > @@ -1819,8 +1819,11 @@ static struct dentry *cgroup_mount(struct file_system_type *fs_type, > goto out_unlock; > } > > - if (root->flags ^ opts.flags) > - pr_warn("new mount options do not match the existing superblock, will be ignored\n"); > + if (root->flags ^ opts.flags) { > + pr_warn("new mount options do not match the existing superblock\n"); > + ret = -EBUSY; > + goto out_unlock; > + } Do we really need the above chunk? > @@ -1909,7 +1912,7 @@ static void cgroup_kill_sb(struct super_block *sb) > * > * And don't kill the default root. > */ > - if (css_has_online_children(&root->cgrp.self) || > + if (!list_empty(&root->cgrp.self.children) || > root == &cgrp_dfl_root) > cgroup_put(&root->cgrp); I tried to do something a bit more advanced so that eventual async release of dying children, if they happen, can also release the hierarchy but I don't think it really matters unless we can forcefully drain. So, shouldn't just the above part be enough? Thanks. -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-01-22 14:35 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-09 17:43 [Regression] 3.19-rc3 : memcg: Hang in mount memcg Suzuki K. Poulose 2015-01-09 17:43 ` Suzuki K. Poulose 2015-01-09 21:46 ` Tejun Heo 2015-01-09 21:46 ` Tejun Heo 2015-01-12 17:02 ` Suzuki K. Poulose 2015-01-12 17:02 ` Suzuki K. Poulose 2015-01-10 8:55 ` Vladimir Davydov 2015-01-10 8:55 ` Vladimir Davydov 2015-01-10 21:43 ` [PATCH cgroup/for-3.19-fixes] cgroup: implement cgroup_subsys->unbind() callback Tejun Heo 2015-01-10 21:43 ` Tejun Heo 2015-01-11 20:55 ` Johannes Weiner 2015-01-11 20:55 ` Johannes Weiner 2015-01-12 8:01 ` Vladimir Davydov 2015-01-12 8:01 ` Vladimir Davydov 2015-01-12 11:28 ` Tejun Heo 2015-01-12 11:28 ` Tejun Heo 2015-01-12 12:59 ` Vladimir Davydov 2015-01-12 12:59 ` Vladimir Davydov 2015-01-12 13:05 ` Tejun Heo 2015-01-12 13:05 ` Tejun Heo 2015-01-14 11:16 ` Suzuki K. Poulose 2015-01-14 11:16 ` Suzuki K. Poulose 2015-01-15 17:56 ` Michal Hocko 2015-01-15 17:56 ` Michal Hocko 2015-01-15 17:26 ` Michal Hocko 2015-01-15 17:26 ` Michal Hocko 2015-01-19 12:51 ` [Regression] 3.19-rc3 : memcg: Hang in mount memcg Suzuki K. Poulose 2015-01-19 12:51 ` Suzuki K. Poulose 2015-01-21 16:39 ` Will Deacon 2015-01-21 16:39 ` Will Deacon 2015-01-22 13:45 ` Johannes Weiner 2015-01-22 13:45 ` Johannes Weiner 2015-01-22 14:34 ` Tejun Heo [this message] 2015-01-22 14:34 ` Tejun Heo 2015-01-22 15:19 ` Johannes Weiner 2015-01-22 15:19 ` Johannes Weiner 2015-01-22 15:28 ` Tejun Heo 2015-01-22 15:28 ` Tejun Heo 2015-01-23 15:00 ` Suzuki K. Poulose 2015-01-23 15:00 ` Suzuki K. Poulose
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=20150122143454.GA4507@htj.dyndns.org \ --to=tj@kernel.org \ --cc=Suzuki.Poulose@arm.com \ --cc=akpm@linux-foundation.org \ --cc=hannes@cmpxchg.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@suse.cz \ --cc=vdavydov@parallels.com \ --cc=will.deacon@arm.com \ /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: linkBe 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.