All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenXiaoSong <chenxiaosong.chenxiaosong@linux.dev>
To: ZhangGuoDong <zhang.guodong@linux.dev>,
	Steve French <smfrench@gmail.com>
Cc: linux-cifs@vger.kernel.org, chenxiaosong@kylinos.cn
Subject: Re: [PATCH v3 4/5] smb: introduce struct create_posix_ctxt_rsp
Date: Thu, 19 Feb 2026 21:14:52 +0800	[thread overview]
Message-ID: <c9d1c233-facd-4387-bed2-b2c1dbc88cbe@linux.dev> (raw)
In-Reply-To: <75cc11b4-f459-454f-a733-a2f25ee76287@linux.dev>

Hi GuoDong,

The changes to patch 04 should be as follows:

--- a/fs/smb/client/smb2pdu.c
+++ b/fs/smb/client/smb2pdu.c
@@ -2362,9 +2362,9 @@ parse_posix_ctxt(struct create_context *cc, struct
-       posix->ctxt_rsp.nlink = le32_to_cpu(*(__le32 *)(beg + 0));
-       posix->ctxt_rsp.reparse_tag = le32_to_cpu(*(__le32 *)(beg + 4));
-       posix->ctxt_rsp.mode = le32_to_cpu(*(__le32 *)(beg + 8));
+       posix->ctxt_rsp.nlink = *(__le32 *)(beg + 0);
+       posix->ctxt_rsp.reparse_tag = *(__le32 *)(beg + 4);
+       posix->ctxt_rsp.mode = *(__le32 *)(beg + 8);

Thanks,
ChenXiaoSong <chenxiaosong@kylinos.cn>

On 2026/2/19 16:16, ChenXiaoSong wrote:
> The changes in parse_posix_ctxt() seem to be fixing a bug. Perhaps we 
> should submit it as a separate bugfix patch (add Reported-by: kernel 
> test robot).
> 
> Steve, what do you think?
> 
> Thanks,
> ChenXiaoSong <chenxiaosong@kylinos.cn>
> 
> On 2026/2/19 15:19, ZhangGuoDong wrote:
>> I can now see these warnings. We should make the following changes, 
>> what do you think?
>>
>> --- a/fs/smb/client/cifsglob.h
>> +++ b/fs/smb/client/cifsglob.h
>> @@ -1270,7 +1270,7 @@ struct cifs_tcon {
>> -       __u32 vol_serial_number;
>> +       __le32 vol_serial_number;
>>
>> --- a/fs/smb/client/smb2pdu.c
>> +++ b/fs/smb/client/smb2pdu.c
>> @@ -2362,9 +2362,9 @@ parse_posix_ctxt(struct create_context *cc, 
>> struct smb2_file_all_info *info,
>> -       posix->ctxt_rsp.nlink = le32_to_cpu(*(__le32 *)(beg + 0));
>> -       posix->ctxt_rsp.reparse_tag = le32_to_cpu(*(__le32 *)(beg + 4));
>> -       posix->ctxt_rsp.mode = le32_to_cpu(*(__le32 *)(beg + 8));
>> +       posix->ctxt_rsp.nlink = cpu_to_le32(*(u32 *)(beg + 0));
>> +       posix->ctxt_rsp.reparse_tag = cpu_to_le32(*(u32 *)(beg + 4));
>> +       posix->ctxt_rsp.mode = cpu_to_le32(*(u32 *)(beg + 8));

  reply	other threads:[~2026-02-19 13:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16  8:20 [PATCH v3 0/5] smb: move duplicate definitions into common header file, part 2 zhang.guodong
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 [this message]
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=c9d1c233-facd-4387-bed2-b2c1dbc88cbe@linux.dev \
    --to=chenxiaosong.chenxiaosong@linux.dev \
    --cc=chenxiaosong@kylinos.cn \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=zhang.guodong@linux.dev \
    /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.