From: David Howells <dhowells@redhat.com>
To: Abel Vesa <abel.vesa@nxp.com>
Cc: dhowells@redhat.com,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: PROBLEM: fs: hugetlbfs: boot failure due to specs sentinel missing on linux-next
Date: Mon, 04 Feb 2019 14:04:09 +0000 [thread overview]
Message-ID: <12006.1549289049@warthog.procyon.org.uk> (raw)
In-Reply-To: <20190204135403.ttitgfy22cp7h2lh@fsr-ub1664-175>
Abel Vesa <abel.vesa@nxp.com> wrote:
> Your commit:
> 2284cf59cbcec "hugetlbfs: Convert to fs_context"
> doesn't put a sentinel at the end of hugetlb_param_specs.
Yes, I have a fix queued for Al to pick up on my mount-api-viro branch (2nd
from bottom, "Fix hugetlbfs").
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?h=container&id=e0e93001d88ab48b40923d926b2cc5e1534407f0
David
prev parent reply other threads:[~2019-02-04 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 13:54 PROBLEM: fs: hugetlbfs: boot failure due to specs sentinel missing on linux-next Abel Vesa
2019-02-04 14:04 ` David Howells [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=12006.1549289049@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=abel.vesa@nxp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).