> On May 27, 2022, at 5:34 PM, Chuck Lever III <chuck.lever@xxxxxxxxxx> wrote: > > > >> On May 27, 2022, at 4:37 PM, Frank van der Linden <fllinden@xxxxxxxxxx> wrote: >> >> On Fri, May 27, 2022 at 06:59:47PM +0000, Chuck Lever III wrote: >>> >>> >>> Hi Frank- >>> >>> Bruce recently reminded me about this issue. Is there a bugzilla somewhere? >>> Do you have a reproducer I can try? >> >> Hi Chuck, >> >> The easiest way to reproduce the issue is to run generic/531 over an >> NFSv4 mount, using a system with a larger number of CPUs on the client >> side (or just scaling the test up manually - it has a calculation based >> on the number of CPUs). >> >> The test will take a long time to finish. I initially described the >> details here: >> >> https://lore.kernel.org/linux-nfs/20200608192122.GA19171@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/ >> >> Since then, it was also reported here: >> >> https://lore.kernel.org/all/20210531125948.2D37.409509F4@xxxxxxxxxxxx/T/#m8c3e4173696e17a9d5903d2a619550f352314d20 > > Thanks for the summary. So, there isn't a bugzilla tracking this > issue? If not, please create one here: > > https://bugzilla.linux-nfs.org/ > > Then we don't have to keep asking for a repeat summary ;-) I can easily reproduce this scenario in my lab. I've opened: https://bugzilla.linux-nfs.org/show_bug.cgi?id=386 -- Chuck Lever
