Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: ChenXiaoSong <chenxiaosong.chenxiaosong@linux.dev>
To: chenxiaosong.chenxiaosong@linux.dev, smfrench@gmail.com,
	linkinjeon@kernel.org, pc@manguebit.org,
	ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
	bharathsm@microsoft.com, senozhatsky@chromium.org,
	dhowells@redhat.com
Cc: linux-cifs@vger.kernel.org, Steve French <stfrench@microsoft.com>
Subject: Re: [PATCH v8 2/5] cifs: Autogenerate SMB2 error mapping table
Date: Fri, 16 Jan 2026 16:14:15 +0800	[thread overview]
Message-ID: <983350d5-aace-4db4-a20b-c1866bfd7bf3@linux.dev> (raw)
In-Reply-To: <20260106071507.1420900-3-chenxiaosong.chenxiaosong@linux.dev>

In this patch, I added the following comments to make the code easier to 
understand. Please see GitHub repository tag `smb2maperror`: 
https://github.com/chenxiaosonggithub/linux/commits/smb2maperror/

--- a/fs/smb/common/smb2status.h
+++ b/fs/smb/common/smb2status.h
@@ -27,6 +27,12 @@ struct ntstatus {
         __le32 Code;
  };

+/*
+ * The comment at the end of each definition indicates `posix_error`
+ * field of `struct status_to_posix_error`, it is used to generate the
+ * `smb2_error_map_table` array.
+ */
+
  #define STATUS_SUCCESS                         cpu_to_le32(0x00000000) 
// 0
  #define STATUS_WAIT_0                          cpu_to_le32(0x00000000) 
// 0
  #define STATUS_WAIT_1                          cpu_to_le32(0x00000001) 
// -EIO

Thanks,
ChenXiaoSong <chenxiaosong@kylinos.cn>

On 1/6/26 15:15, chenxiaosong.chenxiaosong@linux.dev wrote:
> From: David Howells<dhowells@redhat.com>
> 
> Autogenerate the SMB2 status to error code mapping table, from the
> smb2status.h common header, sorting it by NT status code so that it can be
> searched by binary chopping. This also reduces the number of places this
> list is duplicated in the source.


  reply	other threads:[~2026-01-16  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  7:15 [PATCH v8 0/5] smb: improve search speed of SMB2 maperror chenxiaosong.chenxiaosong
2026-01-06  7:15 ` [PATCH v8 1/5] cifs: Label SMB2 statuses with errors chenxiaosong.chenxiaosong
2026-01-06  7:15 ` [PATCH v8 2/5] cifs: Autogenerate SMB2 error mapping table chenxiaosong.chenxiaosong
2026-01-16  8:14   ` ChenXiaoSong [this message]
2026-01-16 13:48   ` Aurélien Aptel
2026-01-16 14:30     ` ChenXiaoSong
2026-01-16 14:51     ` ChenXiaoSong
2026-01-06  7:15 ` [PATCH v8 3/5] smb/client: check whether smb2_error_map_table is sorted in ascending order chenxiaosong.chenxiaosong
2026-01-06  7:15 ` [PATCH v8 4/5] smb/client: use bsearch() to find target in smb2_error_map_table chenxiaosong.chenxiaosong
2026-01-06  7:15 ` [PATCH v8 5/5] smb/client: introduce KUnit test to check search result of smb2_error_map_table chenxiaosong.chenxiaosong
2026-01-06  9:34 ` [PATCH v8 0/5] smb: improve search speed of SMB2 maperror David Howells

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=983350d5-aace-4db4-a20b-c1866bfd7bf3@linux.dev \
    --to=chenxiaosong.chenxiaosong@linux.dev \
    --cc=bharathsm@microsoft.com \
    --cc=dhowells@redhat.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@manguebit.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=senozhatsky@chromium.org \
    --cc=smfrench@gmail.com \
    --cc=sprasad@microsoft.com \
    --cc=stfrench@microsoft.com \
    --cc=tom@talpey.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