[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180718132957.GA17254@kroah.com>
Date: Wed, 18 Jul 2018 15:29:57 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Krzysztof Kozłowski <k.kozlowski.k@...il.com>
Cc: David Howells <dhowells@...hat.com>, Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Tejun Heo <tj@...nel.org>, cgroups@...r.kernel.org,
fenghua.yu@...el.com,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [BUG BISECT] "Support fs_context" causes systemd issues
(linux-next)
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
Powered by blists - more mailing lists