From: "Pali Rohár" <pali@kernel.org>
To: Paulo Alcantara <pc@manguebit.com>
Cc: Ralph Boehme <slow@samba.org>,
Steven French <Steven.French@microsoft.com>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: Special files broken against Samba master
Date: Mon, 9 Dec 2024 20:54:20 +0100 [thread overview]
Message-ID: <20241209195420.7mnya3ua2y7nl6tp@pali> (raw)
In-Reply-To: <829df5e75aba7f0857ff688689b52676@manguebit.com>
On Monday 09 December 2024 16:42:54 Paulo Alcantara wrote:
> Pali Rohár <pali@kernel.org> writes:
>
> > On Monday 09 December 2024 16:28:08 Paulo Alcantara wrote:
> >>
> >> Yes. Have you sent a patch with the proposed solution yet?
> >
> > I have not sent, I was not working on it. I was in impression that you
> > are going to implement the proper solution.
>
> Yes, but priorities have changed, unfortunately.
Ok. Would you have a time to prepare a patch? I have still feeling that
the smb2_compound_op() code and EAs code is rather complicated for me.
I would like if somebody else could look at it, as I have feeling if I
try to do it, it can end up with something more broken...
next prev parent reply other threads:[~2024-12-09 19:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 19:23 Special files broken against Samba master Ralph Boehme
2024-12-02 22:40 ` Paulo Alcantara
2024-12-03 10:02 ` Ralph Boehme
2024-12-03 19:56 ` Steve French
2024-12-03 20:25 ` Ralph Boehme
2024-12-05 0:06 ` Steve French
2024-12-06 12:11 ` Ralph Boehme
2024-12-06 14:45 ` Steve French
2024-12-09 18:39 ` Pali Rohár
2024-12-09 19:28 ` Paulo Alcantara
2024-12-09 19:34 ` Pali Rohár
2024-12-09 19:42 ` Paulo Alcantara
2024-12-09 19:54 ` Pali Rohár [this message]
2024-12-10 13:19 ` Paulo Alcantara
2025-01-01 13:39 ` Pali Rohár
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=20241209195420.7mnya3ua2y7nl6tp@pali \
--to=pali@kernel.org \
--cc=Steven.French@microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=slow@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