From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steve French <sfrench@samba.org>,
Hyunchul Lee <hyc.lee@gmail.com>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ksmbd: Unsupported addition info
Date: Wed, 17 Nov 2021 15:17:08 +0100 [thread overview]
Message-ID: <10049688.nUPlyArG6x@natalenko.name> (raw)
In-Reply-To: <CAKYAXd9wKDTE5WPQWcBZ_mHfaAOOY+pDj7=yndi17gf2KqWpwg@mail.gmail.com>
Hello.
On středa 17. listopadu 2021 10:58:50 CET Namjae Jeon wrote:
> 2021-11-17 16:00 GMT+09:00, Oleksandr Natalenko <oleksandr@natalenko.name>:
> > On středa 17. listopadu 2021 0:36:53 CET Namjae Jeon wrote:
> >> 2021-11-17 6:44 GMT+09:00, Oleksandr Natalenko
> >>
> >> <oleksandr@natalenko.name>:
> >> > With the latest ksmbd from the next branch I have an issue with wife's
> >> > Windows
> >> > 10 laptop while copying/removing files from the network share. On her
> >> > client it
> >> > looks like copy operation (server -> laptop) reaches 99% and then
> >> > stalls,
> >> > and
> >> > on the server side there's this in the kernel log:
> >> >
> >> > ```
> >> > ksmbd: Unsupported addition info: 0xf)
> >> > ksmbd: Unsupported addition info: 0x20)
> >> > ```
> >> >
> >> > repeated multiple times. I must note that in fact the file gets copied
> >> > to
> >> > her
> >> > laptop, but Windows copy dialog just hangs.
> >> >
> >> > Any idea what it could be and how to avoid it? This also happened
> >> > before
> >> > (I'm
> >> > a pretty early ksmbd adopter), but I'm reporting it just now because I
> >> > naïvely
> >> > hoped it would be fixed automagically :). This never happened to me
> >> > with
> >> > userspace Samba though.
> >> >
> >> > This is my smb.conf:
> >> >
> >> > ```
> >> > [global]
> >> > workgroup = KANAPKA
> >> > server string = ksmbd server %v
> >> > netbios name = defiant
> >> > valid users = __guest
> >> >
> >> > [Shared]
> >> > valid users = __guest
> >> > path = /mnt/shared
> >> > force user = _shared
> >> > force group = _shared
> >> > browsable = no
> >> > writeable = yes
> >> > veto files = /lost+found/
> >> > ```
> >> >
> >> > Appreciate your time and looking forward to your response.
> >>
> >> Thanks for your report, I have seen same symptom before, I thought it
> >> was a windows issue as it is also reproduced against samba. If you
> >> wait for a few minutes, does not the 99% message window close?
> >
> > Eventually it does close on its own in a minute or so. Also, it may close
> > after clicking the "X" (close) button, but not instantly.
>
> As I remember, The X button will delete the file you copied.
In my case the file is not deleted. So, probably, it is already copied, but
Windows wants something extra from the share.
> Could you
> please give me packet dump(tcpdump) on problem situation ? and It
> would be nice to give a dump also for a successful copy. I will try to
> compare the two.
Sure.
OK one: [1]
Non-OK one: [2]
Thank you.
[1] https://natalenko.name/myfiles/misc/ksmbd-ok.pcap.gz
[2] https://natalenko.name/myfiles/misc/ksmbd-stalled.pcap.gz
--
Oleksandr Natalenko (post-factum)
next prev parent reply other threads:[~2021-11-17 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 21:44 ksmbd: Unsupported addition info Oleksandr Natalenko
2021-11-16 23:03 ` Marios Makassikis
2021-11-16 23:23 ` Oleksandr Natalenko
2021-11-16 23:36 ` Namjae Jeon
2021-11-17 7:00 ` Oleksandr Natalenko
2021-11-17 9:58 ` Namjae Jeon
2021-11-17 14:17 ` Oleksandr Natalenko [this message]
2021-11-17 17:25 ` Jeremy Allison
2021-11-18 0:31 ` Namjae Jeon
[not found] ` <CAKYAXd_mf9DFQsyzvow=VC6o4xDOn_nncJeo_7gOyG77WfCNqw@mail.gmail.com>
[not found] ` <CAKYAXd-bi-pgFurDF3dfQ0dSZjT0KEDSWK7FtwN5V-Z+FkVgoQ@mail.gmail.com>
[not found] ` <5892347.VCoq2IW8ci@natalenko.name>
2021-11-21 11:26 ` [Test Request] " Namjae Jeon
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=10049688.nUPlyArG6x@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=sfrench@samba.org \
/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