stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.com>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: regressions@lists.linux.dev,
	Steve French <stfrench@microsoft.com>,
	gregkh@linuxfoundation.org, sashal@kernel.org,
	stable@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: [regression 6.1.80+] "CIFS: VFS: directory entry name would overflow frame end of buf" and invisible files under certain conditions and at least with noserverino mount option
Date: Thu, 18 Apr 2024 10:47:01 -0300	[thread overview]
Message-ID: <29e0cbcab5be560608d1dfbfb0ccbc96@manguebit.com> (raw)
In-Reply-To: <ZiCoYjr79HXxiTjr@eldamar.lan>

Salvatore Bonaccorso <carnil@debian.org> writes:

> On Wed, Apr 17, 2024 at 07:58:56PM -0300, Paulo Alcantara wrote:
>> Hi Salvatore,
>> 
>> Salvatore Bonaccorso <carnil@debian.org> writes:
>> 
>> > In Debian we got two reports of cifs mounts not functioning, hiding
>> > certain files. The two reports are:
>> >
>> > https://bugs.debian.org/1069102
>> > https://bugs.debian.org/1069092
>> >
>> > On those cases kernel logs error
>> >
>> > [   23.225952] CIFS: VFS: directory entry name would overflow frame end of buf 00000000a44b272c
>> 
>> I couldn't reproduce it.  Does the following fix your issue:
>> 
>> diff --git a/fs/smb/client/smb2pdu.c b/fs/smb/client/smb2pdu.c
>> index 4c1231496a72..3ee35430595e 100644
>> --- a/fs/smb/client/smb2pdu.c
>> +++ b/fs/smb/client/smb2pdu.c
>> @@ -5083,7 +5083,7 @@ smb2_parse_query_directory(struct cifs_tcon *tcon,
>>  		info_buf_size = sizeof(struct smb2_posix_info);
>>  		break;
>>  	case SMB_FIND_FILE_FULL_DIRECTORY_INFO:
>> -		info_buf_size = sizeof(FILE_FULL_DIRECTORY_INFO);
>> +		info_buf_size = sizeof(FILE_FULL_DIRECTORY_INFO) - 1;
>>  		break;
>>  	default:
>>  		cifs_tcon_dbg(VFS, "info level %u isn't supported\n",
>> 
>> If not, please provide network trace and verbose logs.
>
> Yes that appears to fix the issue.

Thanks for quickly testing it.  So the above change indicates that we're
missing 35235e19b393 ("cifs: Replace remaining 1-element arrays") in
v6.1.y.

Can you test it now with 35235e19b393 backported without the above
change?

> But as you say you are not able to reproduce the issue, I guess we
> need to try to get it clearly reproducible first to see we face no
> other fallouts?

I couldn't reproduce it in v6.9-rc4.  Forgot to mention it, sorry.

Yes, further testing would be great to make sure we're not missing
anything else.

  reply	other threads:[~2024-04-18 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 21:44 [regression 6.1.80+] "CIFS: VFS: directory entry name would overflow frame end of buf" and invisible files under certain conditions and at least with noserverino mount option Salvatore Bonaccorso
2024-04-17 22:58 ` Paulo Alcantara
2024-04-18  4:58   ` Salvatore Bonaccorso
2024-04-18 13:47     ` Paulo Alcantara [this message]
2024-04-19 20:12       ` Salvatore Bonaccorso
2024-04-22 15:08         ` Paulo Alcantara
2024-04-23 20:58           ` Salvatore Bonaccorso
2024-04-29 10:50             ` Greg KH
2024-04-29 15:11               ` Salvatore Bonaccorso

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=29e0cbcab5be560608d1dfbfb0ccbc96@manguebit.com \
    --to=pc@manguebit.com \
    --cc=carnil@debian.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stfrench@microsoft.com \
    /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).