From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
"open list" <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, linux-fsdevel@vger.kernel.org,
autofs@vger.kernel.org
Cc: "Ian Kent" <raven@themaw.net>,
"Bill O'Donnell" <bodonnel@redhat.com>,
"Christian Brauner" <brauner@kernel.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>
Subject: Re: autofs: add autofs_parse_fd()
Date: Fri, 20 Oct 2023 08:36:39 +0200 [thread overview]
Message-ID: <71adfca4-4e80-4a93-b480-3031e26db409@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYt75r4i39DuB4E3y6jRLaLoSEHGbBcJy=AQZBQ2SmBbiQ@mail.gmail.com>
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@linaro.org>
> Reported-by: Anders Roxell <anders.roxell@linaro.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
next prev parent reply other threads:[~2023-10-20 6:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 15:27 Naresh Kamboju
2023-10-20 6:36 ` Arnd Bergmann [this message]
2023-10-20 7:48 ` Naresh Kamboju
2023-10-20 9:02 ` Arnd Bergmann
2023-10-20 9:57 ` Anders Roxell
2023-10-20 13:01 ` Ian Kent
2023-10-20 12:55 ` Ian Kent
2023-10-20 9:55 ` Anders Roxell
2023-10-20 10:45 ` Dan Carpenter
2023-10-20 11:23 ` Arnd Bergmann
2023-10-20 13:09 ` Ian Kent
2023-10-23 0:48 ` Ian Kent
2023-10-23 7:35 ` Ian Kent
2023-10-23 13:57 ` Anders Roxell
2023-10-23 22:24 ` Ian Kent
2023-10-20 12:37 ` Ian Kent
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=71adfca4-4e80-4a93-b480-3031e26db409@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=autofs@vger.kernel.org \
--cc=bodonnel@redhat.com \
--cc=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=raven@themaw.net \
/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
all inboxes | Powered by JetHome®