Re: autofs: add autofs_parse_fd()
Anders Roxell <[email protected]>
| Newsgroups | gmane.linux.kernel,gmane.linux.file-systems,gmane.linux.kernel.autofs |
|---|---|
| Message-ID | <CADYN=9+HDwqAz-eLV7uVuMa+_+foj+_keSG-TmD2imkwVJ_mpQ@mail.gmail.com> |
On Fri, 20 Oct 2023 at 08:37, Arnd Bergmann <[email protected]> wrote: > > 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 <[email protected]> > > Reported-by: Anders Roxell <[email protected]> > > 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? I tried these two patches again: 546694b8f658 ("autofs: add autofs_parse_fd()") - doesn't boot bc69fdde0ae1 ("autofs: refactor autofs_prepare_pipe()") - boots > > What are the exact mount options you pass to autofs in your fstab? cat /etc/fstab # UNCONFIGURED FSTAB FOR BASE SYSTEM Cheers, Anders