From: Paulo Alcantara <pc@cjr.nz>
To: Tom Talpey <tom@talpey.com>,
linux-cifs@vger.kernel.org, smfrench@gmail.com
Subject: Re: [PATCH] cifs: fix bad fids sent over wire
Date: Mon, 21 Mar 2022 12:34:52 -0300 [thread overview]
Message-ID: <875yo7uxnn.fsf@cjr.nz> (raw)
In-Reply-To: <2962692d-a0b5-25f2-3053-7e21620639c9@talpey.com>
Tom Talpey <tom@talpey.com> writes:
> If you want to reduce a bit of code change, you could let the
> compiler generate the loads and stores via memcpy, with (perhaps)
> a struct { u8[8] } instead of the bare array.
Thanks for the suggestions. It turned out to be more changes than I
expected. In this case, I'm gonna fix some remaining sparse warnings
from my last patch and fix the commit message as you suggested.
Of course, we can refactor this out later and start with something like:
struct smb2_fid {
__u8 Persistent[8];
__u8 Volatile[8];
} __packed;
and then replace u64 integers with the above.
next prev parent reply other threads:[~2022-03-21 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 0:20 [PATCH] cifs: fix bad fids sent over wire Paulo Alcantara
2022-03-21 12:10 ` Tom Talpey
2022-03-21 12:30 ` Paulo Alcantara
2022-03-21 12:55 ` Tom Talpey
2022-03-21 15:34 ` Paulo Alcantara [this message]
[not found] ` <CAH2r5muAKvWknawHHYPGpAQ7oiQqTEBaskB8taNK0f9msPaHuQ@mail.gmail.com>
2022-03-21 16:46 ` Tom Talpey
-- strict thread matches above, loose matches on Subject: below --
2022-03-19 4:23 Steve French
2022-03-19 12:06 ` Tom Talpey
[not found] ` <283E0E80-BDAA-45B4-B627-C7BF44C0D126@cjr.nz>
2022-03-19 18:34 ` Steve French
2022-03-20 1:22 ` Namjae Jeon
2022-03-20 1:45 ` Tom Talpey
2022-03-20 2:09 ` Steve French
2022-03-21 2:13 ` ronnie sahlberg
2022-03-21 12:05 ` Tom Talpey
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=875yo7uxnn.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=linux-cifs@vger.kernel.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 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.