From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
GUO Zihua <guozihua@huawei.com>,
v9fs-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] 9p/xen: check logical size for buffer size
Date: Tue, 22 Nov 2022 11:46:13 +0100 [thread overview]
Message-ID: <2955638.xlpIv7zoH0@silver> (raw)
In-Reply-To: <Y3waS1oq4BmitGLT@codewreck.org>
On Tuesday, November 22, 2022 1:39:39 AM CET Dominique Martinet wrote:
> Christian Schoenebeck wrote on Mon, Nov 21, 2022 at 05:35:56PM +0100:
> > Looks good (except of s/rreq/req/ mentioned by Stefano already).
>
> Thanks for the review (I've taken this as a 'reviewed-by' under the
> assumption of that fix, sorry for being a bit aggressive at collecting
> these -- I'd rather overcredit work being done than the other way around)
Yes, you can add my RB of course!
> I'll send this and the three other commits in my 9p-next branch to Linus
> tomorrow around this time:
> https://github.com/martinetd/linux/commits/9p-next
>
>
> > > memcpy(&req->rc, &h, sizeof(h));
> >
> > Is that really OK?
> >
> > 1. `h` is of type xen_9pfs_header and declared as packed, whereas `rc` is
of
> > type p9_fcall not declared as packed.
> >
> > 2. Probably a bit dangerous to assume the layout of xen_9pfs_header being
in
> > sync with the starting layout of p9_fcall without any compile-time
> > assertion?
>
> I've done this in a follow up that will be sent to Linus later as per
> Stefano's suggestion.
Great, one patch less to send, thanks! :)
prev parent reply other threads:[~2022-11-22 10:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 13:55 [PATCH 1/2] 9p/xen: check logical size for buffer size Dominique Martinet
2022-11-18 13:55 ` [PATCH 2/2] 9p: ensure logical size fits allocated size Dominique Martinet
2022-11-19 1:51 ` [PATCH 1/2] 9p/xen: check logical size for buffer size Stefano Stabellini
2022-11-19 2:31 ` Dominique Martinet
2022-11-21 14:16 ` Christian Schoenebeck
2022-11-21 16:35 ` Christian Schoenebeck
2022-11-21 23:01 ` Stefano Stabellini
2022-11-22 0:39 ` Dominique Martinet
2022-11-22 10:46 ` Christian Schoenebeck [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=2955638.xlpIv7zoH0@silver \
--to=linux_oss@crudebyte.com \
--cc=asmadeus@codewreck.org \
--cc=guozihua@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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