From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EF02E17CC for ; Tue, 1 Mar 2022 21:17:10 +0000 (UTC) Received: by mail-lj1-f172.google.com with SMTP id v22so23604689ljh.7 for ; Tue, 01 Mar 2022 13:17:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=16ZNhJ1BQ4Dh3yBBuWi2O3KgukvlyFUrp3KmRTBFO+E=; b=SYQHevikLBA4kamGd2lyFUvor7Y1EJiH9YVEeRdWQJhRi8nTLFTBxKA86OgWcX50eK EcZCVJEoUE+K89kPEWaYjM5tQfLLpQk5c6AMiKBMTGpobq7a89DY4juD1lLiJbyEw8Dt rtfUu4vdB5StzyRx5q2TdZkSz+pE9mIdKo9XE/ujwGyxyUJ1DsQPgFxGXUoJCLHfkOr9 P7s0+YWKQGIayKJw5OgEflxrT0So9fYMmhk0T+Pl8xZOpeyzuz0H2pjxVVSkvpRNPw4S 62pKLtYA7Iy/LX9blTfhnHp0mxSYJ3SuTk+CwQuoBc3xkp1jczRRvafxKGLCVDZrED2a 56ew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=16ZNhJ1BQ4Dh3yBBuWi2O3KgukvlyFUrp3KmRTBFO+E=; b=U3Wf7e1AcQIHhTzmJ0ZRZVBYxsnYNerbOoDiJgDU6p2dppGnbpFP3WmIIqE3QCKrcf 7E9zpoEsdeVsyYG8lw9qVlqN1Rtfn4zVswoJ0q4RGdC4ZGx+j0QRnwrJCnWWNEaPprW4 ++mUVJB4EC/FOrwn8IUi3Lc9oij4yi3UBLo6wO4i0Mc15/MAVDR+WbWK8xyWiC8V6nZ9 o1ZNlzxiIaynkkDIP7/6rLeIJV94Z/fAyn/9xUNjT8maL/3lelZ66sqvvGjVrFbPvdzy 84Bzgzyrh2VLgv03qo4wcpLB+QQzTgufuJp+0DbhcuptZiv56yAQ/DAmpTfKBo7jyccD y2bA== X-Gm-Message-State: AOAM532GSdZS2rsyBFdWfjHDMU0+QdD7a4TEnZqzbAmxKsvS1ix2Fvmr LYcvIzue/o03+45GxYl/B8elo2FYdKIKPd9oEAM= X-Google-Smtp-Source: ABdhPJwTBF7NQJHaPnCRkHxRZae+rdwwh1LyYO7a/yO8OYX2O9Oz2ngXJaGow8TtNMxxmAh0gFdj7Bm+60RPlYqSOmQ= X-Received: by 2002:a05:651c:12c5:b0:23e:1f55:35b4 with SMTP id 5-20020a05651c12c500b0023e1f5535b4mr17904306lje.58.1646169428651; Tue, 01 Mar 2022 13:17:08 -0800 (PST) Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: In-Reply-To: From: Satadru Pramanik Date: Tue, 1 Mar 2022 16:16:57 -0500 Message-ID: Subject: Re: Failure to access cifs mount of samba share after resume from sleep with 5.17-rc5 To: Steve French Cc: Thorsten Leemhuis , CIFS , "regressions@lists.linux.dev" Content-Type: text/plain; charset="UTF-8" I have put the trace.dat and other debug files here since I can not attach the files to a message to the list. (Apparently the trace.dat file is too large.) https://drive.google.com/drive/folders/1wEi968RbXxivXMMH8J7XUsHhrxu9OWDX?usp=sharing On Mon, Feb 28, 2022 at 11:12 PM Satadru Pramanik wrote: > > The trace.dat file is attached, covering the period before suspend, > and through wake several hours later, when the mount no longer worked, > and showed the CIFS: VFS: cifs_tree_connect: could not find > superblock: -22 message, and through when I unmounted and remounted > the share, which then started working. > > On Mon, Feb 28, 2022 at 9:31 AM Satadru Pramanik wrote: > > > > Here is the DebugData from before and after from the system with the > > failed mount. > > Both systems are now running 5.17-rc6. > > > > Working on the trace-cmd now. > > > > On Sun, Feb 27, 2022 at 9:37 PM Steve French wrote: > > > > > > I would like to see the output of: > > > > > > /proc/fs/cifs/DebugData before and after the failure if possible. > > > > > > In addition, there would be some value in seeing trace information > > > (e.g start tracing by > > > "trace-cmd record -e cifs" before the failure and then forward the > > > debug information displayed by "trace-cmd show" after the failure) > > > > > > On Sun, Feb 27, 2022 at 7:55 AM Thorsten Leemhuis > > > wrote: > > > > > > > > [TLDR: I'm adding the regression report below to regzbot, the Linux > > > > kernel regression tracking bot; all text you find below is compiled from > > > > a few templates paragraphs you might have encountered already already > > > > from similar mails.] > > > > > > > > Hi, this is your Linux kernel regression tracker. Top-posting for once, > > > > to make this easily accessible to everyone. > > > > > > > > CCing the regression mailing list, as it should be in the loop for all > > > > regressions, as explained here: > > > > https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html > > > > > > > > To be sure below issue doesn't fall through the cracks unnoticed, I'm > > > > adding it to regzbot, my Linux kernel regression tracking bot: > > > > > > > > #regzbot ^introduced v5.16.11..v5.17-rc5 > > > > #regzbot title cifs: Failure to access cifs mount of samba share after > > > > resume from sleep > > > > #regzbot ignore-activity > > > > > > > > Reminder for developers: when fixing the issue, please add a 'Link:' > > > > tags pointing to the report (the mail quoted above) using > > > > lore.kernel.org/r/, as explained in > > > > 'Documentation/process/submitting-patches.rst' and > > > > 'Documentation/process/5.Posting.rst'. This allows the bot to connect > > > > the report with any patches posted or committed to fix the issue; this > > > > again allows the bot to show the current status of regressions and > > > > automatically resolve the issue when the fix hits the right tree. > > > > > > > > I'm sending this to everyone that got the initial report, to make them > > > > aware of the tracking. I also hope that messages like this motivate > > > > people to directly get at least the regression mailing list and ideally > > > > even regzbot involved when dealing with regressions, as messages like > > > > this wouldn't be needed then. And don't worry, if I need to send other > > > > mails regarding this regression only relevant for regzbot I'll send them > > > > to the regressions lists only (with a tag in the subject so people can > > > > filter them away). With a bit of luck no such messages will be needed > > > > anyway. > > > > > > > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > > > > > > > > P.S.: As the Linux kernel's regression tracker I'm getting a lot of > > > > reports on my table. I can only look briefly into most of them and lack > > > > knowledge about most of the areas they concern. I thus unfortunately > > > > will sometimes get things wrong or miss something important. I hope > > > > that's not the case here; if you think it is, don't hesitate to tell me > > > > in a public reply, it's in everyone's interest to set the public record > > > > straight. > > > > > > > > > > > > On 27.02.22 03:36, Satadru Pramanik wrote: > > > > > I'm on a x86_64 ubuntu 22.04 system accessing a similar system running > > > > > samba Version 4.13.14-Ubuntu. Both systems are on ubuntu mainline > > > > > kernel 5.17-rc5. > > > > > > > > > > I have a samba share mounted from my fstab, and file access works fine. > > > > > Upon suspending my system and resuming though, the mounted samba share > > > > > is inaccessible, and my dmesg has many "CIFS: VFS: cifs_tree_connect: > > > > > could not find superblock: -22" messages. > > > > > > > > > > Unmounting and remounting the share restores access. > > > > > > > > > > When I boot into kernel 5.16.11, I do not have this issue. The cifs > > > > > share is accessible just fine after a suspend/resume cycle. > > > > > > > > > > I assume this is a regression with 5.17? Is there any information > > > > > worth providing which might help debug and fix this issue? > > > > > > > > > > Regards, > > > > > > > > > > Satadru Pramanik > > > > > > > > -- > > > > Additional information about regzbot: > > > > > > > > If you want to know more about regzbot, check out its web-interface, the > > > > getting start guide, and the references documentation: > > > > > > > > https://linux-regtracking.leemhuis.info/regzbot/ > > > > https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md > > > > https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md > > > > > > > > The last two documents will explain how you can interact with regzbot > > > > yourself if your want to. > > > > > > > > Hint for reporters: when reporting a regression it's in your interest to > > > > CC the regression list and tell regzbot about the issue, as that ensures > > > > the regression makes it onto the radar of the Linux kernel's regression > > > > tracker -- that's in your interest, as it ensures your report won't fall > > > > through the cracks unnoticed. > > > > > > > > Hint for developers: you normally don't need to care about regzbot once > > > > it's involved. Fix the issue as you normally would, just remember to > > > > include 'Link:' tag in the patch descriptions pointing to all reports > > > > about the issue. This has been expected from developers even before > > > > regzbot showed up for reasons explained in > > > > 'Documentation/process/submitting-patches.rst' and > > > > 'Documentation/process/5.Posting.rst'. > > > > > > > > > > > > -- > > > Thanks, > > > > > > Steve