The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] Make CONFIG_FHANDLE default y
Date: Thu, 31 Mar 2016 20:46:58 +0200	[thread overview]
Message-ID: <56FD70A2.4060108@nod.at> (raw)
In-Reply-To: <20160331184221.GK7982@two.firstfloor.org>

Am 31.03.2016 um 20:42 schrieb Andi Kleen:
> On Thu, Mar 31, 2016 at 05:52:52PM +0200, Richard Weinberger wrote:
>> On Thu, Mar 31, 2016 at 5:24 PM, Andi Kleen <andi@firstfloor.org> wrote:
>>> From: Andi Kleen <ak@linux.intel.com>
>>>
>>> Newer Fedora and OpenSUSE didn't boot with my standard configuration.
>>> It took me some time to figure out why, in fact I had to write a script
>>> to try different config options systematically.
>>>
>>> The problem is that something in dracut depends on CONFIG_FHANDLE,
>>> which adds open by file handle syscalls.
>>
>> s/something/systemd. :-)
> 
> Makes sense thanks. It should probably give a better error message
> like it gives for missing cgroups
> (right now just your root file system is missing)

That's an improvement, a few release ago it segfaulted in that case.

> But right now we should avoid others having the same pain
> and make the option default.

FHANDLE is part of x86's defconfig.

Please see https://github.com/systemd/systemd/blob/master/README#L37 for a list
of needed kernel options.

Thanks,
//richard

      reply	other threads:[~2016-03-31 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31 15:24 [PATCH] Make CONFIG_FHANDLE default y Andi Kleen
2016-03-31 15:52 ` Richard Weinberger
2016-03-31 18:42   ` Andi Kleen
2016-03-31 18:46     ` Richard Weinberger [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=56FD70A2.4060108@nod.at \
    --to=richard@nod.at \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox