From: ChenXiaoSong <chenxiaosong.chenxiaosong@linux.dev>
To: Steve French <smfrench@gmail.com>
Cc: linkinjeon@kernel.org, linkinjeon@samba.org,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
chenxiaosong@chenxiaosong.com,
ChenXiaoSong <chenxiaosong@kylinos.cn>,
samba-technical <samba-technical@lists.samba.org>
Subject: Re: [PATCH 01/10] smb/client: reduce loop count in map_smb2_to_linux_error() by half
Date: Thu, 4 Dec 2025 13:55:16 +0800 [thread overview]
Message-ID: <af214141-4a8f-4d79-819c-26edb016be66@linux.dev> (raw)
In-Reply-To: <CAH2r5mu25T8sBO4P25St_H0F0KMenn+5QGWx1Tfa+=6AsF6aNw@mail.gmail.com>
Thanks for your review.
I'll test these patches as soon as possible. Besides smbtorture and
xfstests, what other testing tools are available for SMB?
Thanks,
ChenXiaoSong.
On 12/4/25 13:49, Steve French wrote:
> Have merged the first three patches (see below) in this series into
> cifs-2.6.git for-next pending additional review and testing. The
> other seven may also be ok - but want to look more carefully at them,
> more review appreciated
>
> ba521f56912f (HEAD -> for-next, origin/for-next) smb: add two elements
> to smb2_error_map_table array
> 905d8999d67d smb/client: remove unused elements from smb2_error_map_table array
> 26866d690bd1 smb/client: reduce loop count in map_smb2_to_linux_error() by half
>
> On Wed, Dec 3, 2025 at 10:59 PM <chenxiaosong.chenxiaosong@linux.dev> wrote:
>>
>> From: ChenXiaoSong <chenxiaosong@kylinos.cn>
>>
>> The smb2_error_map_table array currently has 1740 elements. When searching
>> for the last element and calling smb2_print_status(), 3480 comparisons
>> are needed.
>>
>> The loop in smb2_print_status() is unnecessary, smb2_print_status() can be
>> removed, and only iterate over the array once, printing the message when
>> the target status code is found.
>>
>> Signed-off-by: ChenXiaoSong <chenxiaosong@kylinos.cn>
>> ---
>> fs/smb/client/smb2maperror.c | 30 ++++++------------------------
>> 1 file changed, 6 insertions(+), 24 deletions(-)
>>
>> diff --git a/fs/smb/client/smb2maperror.c b/fs/smb/client/smb2maperror.c
>> index 12c2b868789f..d1df6e518d21 100644
>> --- a/fs/smb/client/smb2maperror.c
>> +++ b/fs/smb/client/smb2maperror.c
>> @@ -2418,24 +2418,6 @@ static const struct status_to_posix_error smb2_error_map_table[] = {
>> {0, 0, NULL}
>> };
>>
>> -/*****************************************************************************
>> - Print an error message from the status code
>> - *****************************************************************************/
>> -static void
>> -smb2_print_status(__le32 status)
>> -{
>> - int idx = 0;
>> -
>> - while (smb2_error_map_table[idx].status_string != NULL) {
>> - if ((smb2_error_map_table[idx].smb2_status) == status) {
>> - pr_notice("Status code returned 0x%08x %s\n", status,
>> - smb2_error_map_table[idx].status_string);
>> - }
>> - idx++;
>> - }
>> - return;
>> -}
>> -
>> int
>> map_smb2_to_linux_error(char *buf, bool log_err)
>> {
>> @@ -2452,16 +2434,16 @@ map_smb2_to_linux_error(char *buf, bool log_err)
>> return 0;
>> }
>>
>> - /* mask facility */
>> - if (log_err && (smb2err != STATUS_MORE_PROCESSING_REQUIRED) &&
>> - (smb2err != STATUS_END_OF_FILE))
>> - smb2_print_status(smb2err);
>> - else if (cifsFYI & CIFS_RC)
>> - smb2_print_status(smb2err);
>> + log_err = (log_err && (smb2err != STATUS_MORE_PROCESSING_REQUIRED) &&
>> + (smb2err != STATUS_END_OF_FILE)) ||
>> + (cifsFYI & CIFS_RC);
>>
>> for (i = 0; i < sizeof(smb2_error_map_table) /
>> sizeof(struct status_to_posix_error); i++) {
>> if (smb2_error_map_table[i].smb2_status == smb2err) {
>> + if (log_err)
>> + pr_notice("Status code returned 0x%08x %s\n", smb2err,
>> + smb2_error_map_table[i].status_string);
>> rc = smb2_error_map_table[i].posix_error;
>> break;
>> }
>> --
>> 2.43.0
>>
>
>
next prev parent reply other threads:[~2025-12-04 5:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 4:58 [PATCH 00/10] smb: improve search speed of SMB2 maperror chenxiaosong.chenxiaosong
2025-12-04 4:58 ` [PATCH 01/10] smb/client: reduce loop count in map_smb2_to_linux_error() by half chenxiaosong.chenxiaosong
2025-12-04 5:49 ` Steve French
2025-12-04 5:55 ` ChenXiaoSong [this message]
2025-12-04 4:58 ` [PATCH 02/10] smb/client: remove unused elements from smb2_error_map_table array chenxiaosong.chenxiaosong
2025-12-04 4:58 ` [PATCH 03/10] smb: add two elements to " chenxiaosong.chenxiaosong
2025-12-04 4:58 ` [PATCH 04/10] smb/client: sort " chenxiaosong.chenxiaosong
2025-12-04 4:58 ` [PATCH 05/10] smb/client: use bsearch() to find target status code chenxiaosong.chenxiaosong
2025-12-04 4:58 ` [PATCH 06/10] smb/client: introduce smb2_get_err_map() chenxiaosong.chenxiaosong
2025-12-04 4:58 ` [PATCH 07/10] smb/client: introduce smb2maperror KUnit tests chenxiaosong.chenxiaosong
2025-12-04 4:58 ` [PATCH 08/10] smb/server: rename include guard in smb_common.h chenxiaosong.chenxiaosong
2025-12-04 4:58 ` [PATCH 09/10] smb: create common/common.h and common/common.c chenxiaosong.chenxiaosong
2025-12-05 0:35 ` Namjae Jeon
2025-12-05 0:58 ` ChenXiaoSong
2025-12-05 1:36 ` Steve French
2025-12-05 1:44 ` ChenXiaoSong
2025-12-05 1:50 ` Steve French
2025-12-05 2:14 ` ChenXiaoSong
2025-12-05 3:02 ` ChenXiaoSong
2025-12-04 4:58 ` [PATCH 10/10] smb: move client/smb2maperror.c to common/ chenxiaosong.chenxiaosong
2025-12-04 20:39 ` kernel test robot
2025-12-04 21:12 ` kernel test robot
2025-12-05 2:35 ` kernel test robot
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=af214141-4a8f-4d79-819c-26edb016be66@linux.dev \
--to=chenxiaosong.chenxiaosong@linux.dev \
--cc=chenxiaosong@chenxiaosong.com \
--cc=chenxiaosong@kylinos.cn \
--cc=linkinjeon@kernel.org \
--cc=linkinjeon@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.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