From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 5.4 000/191] 5.4.8-stable review
Date: Sat, 4 Jan 2020 10:06:06 +0100 [thread overview]
Message-ID: <20200104090606.GA1249964@kroah.com> (raw)
In-Reply-To: <8283b231-f6e8-876f-7094-d3265096ab9a@oracle.com>
On Fri, Jan 03, 2020 at 09:56:52AM -0800, Mike Kravetz wrote:
> On 1/3/20 9:33 AM, Mike Kravetz wrote:
> > On 1/3/20 7:56 AM, Arnd Bergmann wrote:
> >> On Fri, Jan 3, 2020 at 4:45 PM Greg Kroah-Hartman
> >> <gregkh@linuxfoundation.org> wrote:
> >>> On Fri, Jan 03, 2020 at 04:29:56PM +0100, Arnd Bergmann wrote:
> >>>> On Fri, Jan 3, 2020 at 4:25 PM Arnd Bergmann <arnd@arndb.de> wrote:
> >>>>>
> >>>>> On Fri, Jan 3, 2020 at 4:03 PM Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >>>>>>
> >>>>>> On Fri, 3 Jan 2020 at 03:42, Greg Kroah-Hartman
> >>>>>> <gregkh@linuxfoundation.org> wrote:
> >>>>>
> >>>>> -ENOENT is what you get when hugetlbfs is not mounted, so this hints to
> >>>>>
> >>>>> 8fc312b32b2 mm/hugetlbfs: fix error handling when setting up mounts
> >>>>>
> >>>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-5.4.y&id=3f549fb42a39bea3b29c0fc12afee53c4a01bec9
> >>>>
> >>>> I see that Mike Kravetz suggested not putting this patch into stable in
> >>>>
> >>>> https://lore.kernel.org/lkml/befca227-cb8a-8f47-617d-e3bf9972bfec@oracle.com/
> >>>>
> >>>> but it was picked through the autosel mechanism later.
> >>>
> >>> So does that mean that Linus's tree shows this LTP failure as well?
> >>
> >> Yes, according to
> >> https://qa-reports.linaro.org/lkft/linux-mainline-oe/tests/ltp-syscalls-tests/memfd_create04
> >> mainline has the same testcase failure, it started happening between
> >> v5.4-10135-gc3bfc5dd73c6 and v5.4-10271-g596cf45cbf6e, when the patch
> >> was originally merged into 5.5-rc1.
> >>
> >>> This does seem to fix a real issue, as shown by the LTP test noticing
> >>> it, so should the error code value be fixed in Linus's tree?
> >>
> >> No idea what to conclude from the testcase failure, let's see if Mike has
> >> any suggestions.
> >>
> >
> > Thanks for isolating to this patch!
> >
> > There are dependencies between arch specific code and arch independent code
> > during the setup of hugetlb sizes/mounts. Let me take a closer look at the
> > arm64 code and get access to a system for debug.
>
> Before I started investigating, Jan Stancek found and fixed the issue.
>
> http://lkml.kernel.org/r/a14b944b6e5e207d2f84f43227c98ed1f68290a2.1578072927.git.jstancek@redhat.com
Great, thanks for this, now queued up.
greg k-h
next prev parent reply other threads:[~2020-01-04 9:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200102215829.911231638@linuxfoundation.org>
2020-01-03 15:03 ` [LTP] [PATCH 5.4 000/191] 5.4.8-stable review Naresh Kamboju
2020-01-03 15:25 ` Arnd Bergmann
2020-01-03 15:29 ` Arnd Bergmann
2020-01-03 15:45 ` Greg Kroah-Hartman
2020-01-03 15:56 ` Arnd Bergmann
2020-01-03 17:33 ` Mike Kravetz
2020-01-03 17:56 ` Mike Kravetz
2020-01-03 18:40 ` Linus Torvalds
2020-01-03 19:11 ` Thomas Backlund
2020-01-03 19:23 ` Linus Torvalds
2020-01-03 22:15 ` Thomas Backlund
2020-01-06 9:03 ` Naresh Kamboju
2020-01-04 9:06 ` Greg Kroah-Hartman [this message]
2020-01-03 15:48 ` Guenter Roeck
2020-01-03 16:30 ` Greg Kroah-Hartman
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=20200104090606.GA1249964@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ltp@lists.linux.it \
/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