From: zhang.guodong@linux.dev
To: 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, chenxiaosong@kylinos.cn,
chenxiaosong.chenxiaosong@linux.dev
Cc: linux-cifs@vger.kernel.org, ZhangGuoDong <zhangguodong@kylinos.cn>
Subject: [PATCH v3 0/5] smb: move duplicate definitions into common header file, part 2
Date: Mon, 16 Feb 2026 08:20:13 +0000 [thread overview]
Message-ID: <20260216082018.156695-1-zhang.guodong@linux.dev> (raw)
From: ZhangGuoDong <zhangguodong@kylinos.cn>
v2->v3:
- Patch #01: "__u32 VolumeSerialNumber" -> "__le32 VolumeSerialNumber"
- Patch #02: rebased on cifs-2.6.git for-next
- Add patch #03
v1: https://lore.kernel.org/all/20251209011020.3270989-1-chenxiaosong.chenxiaosong@linux.dev/
v2: https://lore.kernel.org/linux-cifs/20251211143228.172470-1-chenxiaosong.chenxiaosong@linux.dev/
The following patches from v1 and v2 have already been merged into mainline:
- 94d5b8dbc5d9 smb: move some SMB1 definitions into common/smb1pdu.h
- 2b6abb893e71 smb: move File Attributes definitions into common/fscc.h
- c97503321ed3 smb: update struct duplicate_extents_to_file_ex
- 2e0d224d8988 smb/server: add comment to FileSystemName of FileFsAttributeInformation
- ab0347e67dac smb/client: remove DeviceType Flags and Device Characteristics definitions
- 08c2a7d2bae9 smb: move file_notify_information to common/fscc.h
- 6539e18517b6 smb: move SMB2 Notify Action Flags into common/smb2pdu.h
- 9ec7629b430a smb: move notify completion filter flags into common/smb2pdu.h
- bcdd6cfaf2ec smb: add documentation references for smb2 change notify definitions
This is a continuous effort to move duplicated definitions in both client
and server into common header files, which makes the code easier to maintain.
The previous work is here:
- part 1: https://lore.kernel.org/linux-cifs/20251117112838.473051-1-chenxiaosong.chenxiaosong@linux.dev/
ZhangGuoDong (5):
smb: move smb3_fs_vol_info into common/fscc.h
smb: move some definitions from common/smb2pdu.h into common/fscc.h
smb: move file_basic_info into common/fscc.h
smb: introduce struct create_posix_ctxt_rsp
smb: introduce struct file_posix_info
fs/smb/client/inode.c | 22 +--
fs/smb/client/readdir.c | 28 +--
fs/smb/client/reparse.h | 4 +-
fs/smb/client/smb1pdu.h | 9 -
fs/smb/client/smb2pdu.c | 9 +-
fs/smb/client/smb2pdu.h | 21 +-
fs/smb/common/fscc.h | 379 ++++++++++++++++++++++++++++++++++++-
fs/smb/common/smb2pdu.h | 360 ++---------------------------------
fs/smb/server/oplock.c | 8 +-
fs/smb/server/smb2pdu.c | 98 +++++-----
fs/smb/server/smb2pdu.h | 36 +---
fs/smb/server/smb_common.h | 8 -
12 files changed, 486 insertions(+), 496 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-16 8:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 8:20 zhang.guodong [this message]
2026-02-16 8:20 ` [PATCH v3 1/5] smb: move smb3_fs_vol_info into common/fscc.h zhang.guodong
2026-02-16 16:05 ` kernel test robot
2026-02-16 8:20 ` [PATCH v3 2/5] smb: move some definitions from common/smb2pdu.h " zhang.guodong
2026-02-16 8:20 ` [PATCH v3 3/5] smb: move file_basic_info " zhang.guodong
2026-02-16 8:20 ` [PATCH v3 4/5] smb: introduce struct create_posix_ctxt_rsp zhang.guodong
2026-02-16 18:22 ` kernel test robot
2026-02-17 14:20 ` ZhangGuoDong
[not found] ` <CAH2r5muK5WrHkJsJ=Rix7ceFFZNzpQkUZSaSsHi8PMXVpw88pw@mail.gmail.com>
[not found] ` <b840459a-8a31-46e7-817a-3b80e9ed1353@linux.dev>
[not found] ` <CAH2r5muScb7NmeJa1BNwAt8Qzb7WmwVfvskZ=9LEV6WWyO5HyQ@mail.gmail.com>
[not found] ` <d6149e9f-9607-4379-a74d-c4bbe12fef00@linux.dev>
2026-02-19 8:16 ` ChenXiaoSong
2026-02-19 13:14 ` ChenXiaoSong
2026-02-16 8:20 ` [PATCH v3 5/5] smb: introduce struct file_posix_info zhang.guodong
2026-02-20 1:27 ` [PATCH v3 0/5] smb: move duplicate definitions into common header file, part 2 Namjae Jeon
2026-02-20 10:54 ` ZhangGuoDong
2026-02-22 7:39 ` ChenXiaoSong
2026-02-22 15:26 ` ChenXiaoSong
2026-02-22 15:42 ` ChenXiaoSong
2026-02-25 3:14 ` ZhangGuoDong
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=20260216082018.156695-1-zhang.guodong@linux.dev \
--to=zhang.guodong@linux.dev \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong.chenxiaosong@linux.dev \
--cc=chenxiaosong@kylinos.cn \
--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=tom@talpey.com \
--cc=zhangguodong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox