From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Subject: Re: [BUG BISECT] "Support fs_context" causes systemd issues (linux-next) Date: Wed, 18 Jul 2018 15:29:57 +0200 Message-ID: <20180718132957.GA17254@kroah.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Krzysztof =?utf-8?Q?Koz=C5=82owski?= Cc: David Howells , Li Zefan , Johannes Weiner , Tejun Heo , cgroups@vger.kernel.org, fenghua.yu@intel.com, "linux-samsung-soc@vger.kernel.org" , "linux-next@vger.kernel.org" , linux-kernel@vger.kernel.org List-Id: linux-next.vger.kernel.org On Wed, Jul 18, 2018 at 01:46:35PM +0200, Krzysztof Kozłowski wrote: > Hi, > > On recent linux-next, the commit f8076f3b0996 ("kernfs, sysfs, cgroup, > intel_rdt: Support fs_context") causes weird behavior of two of > systemd units: systemd-timesyncd.service and systemd-resolved.service > fail to start. > > Logs: > > Jul 18 09:51:33 odroidu3 systemd[376]: systemd-timesyncd.service: > Failed to set up mount namespacing: Invalid argument Looks like the parsing for kernel mount options is broken somehow in the above patch :( thanks, greg k-h