From: Paulo Alcantara <pc@cjr.nz>
To: "J. Pablo González" <disablez@disablez.com>, linux-cifs@vger.kernel.org
Subject: Re: [Bug report] Since 5.17 kernel, non existing files may be treated as remote DFS entries
Date: Tue, 17 Jan 2023 14:36:01 -0300 [thread overview]
Message-ID: <87y1q1ukqm.fsf@cjr.nz> (raw)
In-Reply-To: <CAF2j4JG_w4XD=LzhPHWAMjA2yRqJ6A4K+x8XZ36d2zJOuZp4KQ@mail.gmail.com>
J. Pablo González <disablez@disablez.com> writes:
> On Mon, Jan 16, 2023 at 2:02 PM Paulo Alcantara <pc@cjr.nz> wrote:
>>
>> J. Pablo González <disablez@disablez.com> writes:
>>
>> > We’re experiencing some issues when accessing some mounts in a DFS
>> > share, which seem to happen since kernel 5.17.
>> >
>> > After some investigation, we’ve pinpointed the origin to commit
>> > a2809d0e16963fdf3984409e47f145
>> > cccb0c6821
>> > - Original BZ for that is https://bugzilla.kernel.org/show_bug.cgi?id=215440
>> > - Patch discussion is at
>> > https://patchwork.kernel.org/project/cifs-client/patch/YeHUxJ9zTVNrKveF@himera.home/
>> > - Similar issues referenced in https://bugzilla.suse.com/show_bug.cgi?id=1198753
>>
>> 6.2-rc4 has
>>
>> c877ce47e137 ("cifs: reduce roundtrips on create/qinfo requests")
>>
>> which should fix your issue.
>>
>> Could you try it? Thanks.
>
> I'll still need to test it more thoroughly, but for now, this patch
> seems to have fixed all issues, including the "-o nodfs ones." Thank
> you!
OK - thanks for quickily testing it!
> Any chance this could be formally backported to 6.1.x ? I see it's
> only tagged for 6.2-rc for now.
Absolutely. Will take care of that.
next prev parent reply other threads:[~2023-01-17 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 2:53 [Bug report] Since 5.17 kernel, non existing files may be treated as remote DFS entries J. Pablo González
2023-01-16 13:02 ` Paulo Alcantara
2023-01-17 0:14 ` J. Pablo González
2023-01-17 17:36 ` Paulo Alcantara [this message]
2023-01-18 22:38 ` Paulo Alcantara
2023-01-22 13:45 ` Greg KH
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=87y1q1ukqm.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=disablez@disablez.com \
--cc=linux-cifs@vger.kernel.org \
/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