[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <71adfca4-4e80-4a93-b480-3031e26db409@app.fastmail.com>
Date: Fri, 20 Oct 2023 08:36:39 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Naresh Kamboju" <naresh.kamboju@...aro.org>,
"open list" <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org, linux-fsdevel@...r.kernel.org,
autofs@...r.kernel.org
Cc: "Ian Kent" <raven@...maw.net>,
"Bill O'Donnell" <bodonnel@...hat.com>,
"Christian Brauner" <brauner@...nel.org>,
"Dan Carpenter" <dan.carpenter@...aro.org>,
"Anders Roxell" <anders.roxell@...aro.org>
Subject: Re: autofs: add autofs_parse_fd()
On Thu, Oct 19, 2023, at 17:27, Naresh Kamboju wrote:
> The qemu-x86_64 and x86_64 booting with 64bit kernel and 32bit rootfs we call
> it as compat mode boot testing. Recently it started to failed to get login
> prompt.
>
> We have not seen any kernel crash logs.
>
> Anders, bisection is pointing to first bad commit,
> 546694b8f658 autofs: add autofs_parse_fd()
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> Reported-by: Anders Roxell <anders.roxell@...aro.org>
I tried to find something in that commit that would be different
in compat mode, but don't see anything at all -- this appears
to be just a simple refactoring of the code, unlike the commits
that immediately follow it and that do change the mount
interface.
Unfortunately this makes it impossible to just revert the commit
on top of linux-next. Can you double-check your bisection by
testing 546694b8f658 and the commit before it again?
What are the exact mount options you pass to autofs in your fstab?
Arnd
Powered by blists - more mailing lists