From: ChenXiaoSong <chenxiaosong.chenxiaosong@linux.dev>
To: Henrique Carvalho <henrique.carvalho@suse.com>,
Steve French <smfrench@gmail.com>
Cc: Youling Tang <tangyouling@kylinos.cn>,
Namjae Jeon <linkinjeon@kernel.org>,
David Howells <dhowells@redhat.com>,
CIFS <linux-cifs@vger.kernel.org>,
Meetakshi Setiya <meetakshisetiyaoss@gmail.com>,
gustavoars@kernel.org
Subject: Re: generic/013 failure to Samba
Date: Sat, 27 Dec 2025 06:48:14 +0800 [thread overview]
Message-ID: <1afdefff-0ce5-4875-b480-0b3aba541d28@linux.dev> (raw)
In-Reply-To: <7duojyv45sv3x65fmaggbhl2rydgisaqesedqqbrk2pg6jyo5m@2cwq23g2sw2v>
I think the comment in your change is easy to understand. Looks good to me.
Steve, what do you think? I see that you have already sent the pull
request for 6.19-rc3. Should we merge Henrique's patch in rc3?
Thanks,
ChenXiaoSong <chenxiaosong@kylinos.cn>
On 12/27/25 2:05 AM, Henrique Carvalho wrote:
> Your change does make the code semantically tighter, since ChunkCount would
> track initialized elements as we populate the array.
>
> That said, I still slightly prefer setting ChunkCount to the allocated
> capacity before we first index Chunks[], and then setting it to the final
> chunks value before the IOCTL.
>
> This both satisfies __counted_by_le() during population, it isn't wrong
> given the allocation is chunk_count, and avoids an extra ChunkCount
> update on every chunk entry (in my build this is not optimized away).
> It's cheap either way, but if we can avoid per-iteration overhead, I'd
> rather do so.
>
> What do you think? Do you see any correctness or tooling downside with
> this approach?
next prev parent reply other threads:[~2025-12-26 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 0:19 generic/013 failure to Samba Steve French
2025-12-24 15:02 ` Henrique Carvalho
2025-12-26 4:36 ` ChenXiaoSong
2025-12-26 6:44 ` ChenXiaoSong
2025-12-26 7:49 ` ChenXiaoSong
2025-12-26 15:45 ` Henrique Carvalho
2025-12-26 16:01 ` ChenXiaoSong
2025-12-26 18:05 ` Henrique Carvalho
2025-12-26 22:48 ` ChenXiaoSong [this message]
[not found] ` <CAH2r5mtaGgiWLnMebWeGNoyVKY81xj6DkZY5iTmWkJZ_gvyeLw@mail.gmail.com>
[not found] ` <7919537a-d3b5-45cd-9032-0a5312b28dfb@linux.dev>
2025-12-26 23:46 ` ChenXiaoSong
2025-12-26 15:33 ` Henrique Carvalho
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=1afdefff-0ce5-4875-b480-0b3aba541d28@linux.dev \
--to=chenxiaosong.chenxiaosong@linux.dev \
--cc=dhowells@redhat.com \
--cc=gustavoars@kernel.org \
--cc=henrique.carvalho@suse.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=meetakshisetiyaoss@gmail.com \
--cc=smfrench@gmail.com \
--cc=tangyouling@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.