regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [Regression 5.17-rc2] Symlink on NFS mount to directory on other NFS mount not resolved on first access #forregzbot
Date: Wed, 16 Feb 2022 10:34:41 +0100	[thread overview]
Message-ID: <6be286ae-5fdd-5545-c35c-3443e07f76c5@leemhuis.info> (raw)
In-Reply-To: <0235e04a-18aa-ccbf-f520-38a2d55e8b54@molgen.mpg.de>

for the record:

#regzbot fixed-by: e0caaf75d443e02e55e146fd75fe2efc8aed5540

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=e0caaf75d443e02e55e146fd75fe2efc8aed5540

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

On 08.02.22 19:13, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> Am 08.02.22 um 15:36 schrieb Paul Menzel:
>> #regzbot introduced: ac795161c93699d600db16c1a8cc23a65a1eceaf
> 
> 
>> Commit ac795161c936 (NFSv4: Handle case where the lookup of a
>> directory fails) [1], part of Linux since 5.17-rc2, introduced a
>> regression, where a symbolic link on an NFS mount to a directory on
>> another NFS does not resolve(?) the first time it is accessed:
> 
> I forgot to include, that we are using autofs/automount for these
> directories.
> 
>> ```
>> $ ls -dl /src/mariux/beeroot/build-archives
>> lrwxrwxrwx 1 root root 39 May  5  2021
>> /src/mariux/beeroot/build-archives ->
>> /src/mariux_data/beeroot/build-archives
>> $ df /src/mariux{,_data}
>> Filesystem                                           1K-blocks Used  
>> Available Use% Mounted on
>> macheteinfach:/amd/macheteinfach/1/src/mariux      17575970816
>> 2930189312 14645781504  17% /src/mariux
>> macheteinfach:/amd/macheteinfach/1/src/mariux_data 17575970816
>> 2930189312 14645781504  17% /src/mariux_data
>>
>> $ sudo umount /src/mariux /src/mariux_data
>> $ echo /src/mariux/beeroot/build-archives/*5.17*
>> /src/mariux/beeroot/build-archives/*5.17*
>> $ strace -e openat echo /src/mariux/beeroot/build-archives/*5.17*
>> openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
>> openat(AT_FDCWD, "/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
>> openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC)
>> = 3
>> /src/mariux/beeroot/build-archives/*5.17*
>> +++ exited with 0 +++
>> $ echo /src/mariux/beeroot/build-archives/*5.17*
>> /src/mariux/beeroot/build-archives/linux-5.17_rc1-423.x86_64.beebuild.tar.bz2
>> /src/mariux/beeroot/build-archives/linux-5.17_rc2-424.x86_64.beebuild.tar.bz2
>> /src/mariux/beeroot/build-archives/linux-5.17_rc3-426.x86_64.beebuild.tar.bz2
>> /src/mariux/beeroot/build-archives/mariux64-caret_R-3.0.2-5.17_7-0.x86_64.beebuild.tar.bz2
>>
>>
>> Using a dot in the path works around the issue:
>>
>> ```
>> $ sudo umount /src/mariux /src/mariux_data
>> $ strace -e openat echo /src/mariux/beeroot/build-archives/./*5.17*
>> openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
>> openat(AT_FDCWD, "/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
>> openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC)
>> = 3
>> /src/mariux/beeroot/build-archives/./linux-5.17_rc1-423.x86_64.beebuild.tar.bz2
>> /src/mariux/beeroot/build-archives/./linux-5.17_rc2-424.x86_64.beebuild.tar.bz2
>> /src/mariux/beeroot/build-archives/./linux-5.17_rc3-426.x86_64.beebuild.tar.bz2
>> /src/mariux/beeroot/build-archives/./mariux64-caret_R-3.0.2-5.17_7-0.x86_64.beebuild.tar.bz2
>>
>> +++ exited with 0 +++
>> ```
> 
> 
> Kind regards,
> 
> Paul
> 
> 
>> [1]:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac795161c93699d600db16c1a8cc23a65a1eceaf
> 
> 
> 

      reply	other threads:[~2022-02-16  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 14:36 [Regression 5.17-rc2] Symlink on NFS mount to directory on other NFS mount not resolved on first access Paul Menzel
2022-02-08 18:13 ` Paul Menzel
2022-02-16  9:34   ` Thorsten Leemhuis [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=6be286ae-5fdd-5545-c35c-3443e07f76c5@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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).