Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Namjae Jeon <linkinjeon@kernel.org>
To: ChenXiaoSong <chenxiaosong@chenxiaosong.com>
Cc: smfrench@gmail.com, pc@manguebit.org, tom@talpey.com,
	 senozhatsky@chromium.org, slow@samba.org,
	linux-cifs@vger.kernel.org,
	 ChenXiaoSong <chenxiaosong@kylinos.cn>
Subject: Re: [PATCH v3 resend 0/3] smb: fix xfstests generic/035
Date: Thu, 6 Aug 2026 08:25:55 +0900	[thread overview]
Message-ID: <CAKYAXd91pPDcSHgJs-_MdBbs0_22Tzb6LL6udVfFMGOYSx9Pbw@mail.gmail.com> (raw)
In-Reply-To: <20260805051112.305078-1-chenxiaosong@chenxiaosong.com>

On Wed, Aug 5, 2026 at 2:12 PM ChenXiaoSong
<chenxiaosong@chenxiaosong.com> wrote:
>
> From: ChenXiaoSong <chenxiaosong@kylinos.cn>
>
> Resending patchset due to mail server issue.
>
> v2->v3:
>   - Patch #02: iterate over `global_ft.idr`.
>
> v2: https://lore.kernel.org/linux-cifs/20260804123301.285434-1-chenxiaosong@chenxiaosong.com/
>
> ChenXiaoSong (3):
>   smb/server: rename to ksmbd_has_nonposix_open_child()
>   smb/server: deny overwriting targets with non-POSIX opens
Applied ksmbd's patches to #ksmbd-for-next-next.
Thanks!

      parent reply	other threads:[~2026-08-05 23:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  5:11 [PATCH v3 resend 0/3] smb: fix xfstests generic/035 ChenXiaoSong
2026-08-05  5:11 ` [PATCH v3 resend 1/3] smb/server: rename to ksmbd_has_nonposix_open_child() ChenXiaoSong
2026-08-05  5:11 ` [PATCH v3 resend 2/3] smb/server: deny overwriting targets with non-POSIX opens ChenXiaoSong
2026-08-05  6:40   ` ChenXiaoSong
2026-08-05  5:11 ` [PATCH v3 resend 3/3] smb/client: fix nlink of an overwritten open file ChenXiaoSong
2026-08-07 10:27   ` hehuiwen
2026-08-05 23:25 ` Namjae Jeon [this message]

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=CAKYAXd91pPDcSHgJs-_MdBbs0_22Tzb6LL6udVfFMGOYSx9Pbw@mail.gmail.com \
    --to=linkinjeon@kernel.org \
    --cc=chenxiaosong@chenxiaosong.com \
    --cc=chenxiaosong@kylinos.cn \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@manguebit.org \
    --cc=senozhatsky@chromium.org \
    --cc=slow@samba.org \
    --cc=smfrench@gmail.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