From: Greg KH <greg@kroah.com>
To: "Xu, Lizhi" <Lizhi.Xu@windriver.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: 回复: 回复: linux-next: build failure after merge of the char-misc tree
Date: Thu, 3 Jul 2025 12:03:07 +0200 [thread overview]
Message-ID: <2025070301-albatross-angriness-00c1@gregkh> (raw)
In-Reply-To: <BL1PR11MB59798DB1C2D7B2B2988BE2DB8643A@BL1PR11MB5979.namprd11.prod.outlook.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Jul 03, 2025 at 09:44:13AM +0000, Xu, Lizhi wrote:
>
> Perhaps you can focus on "struct vmci_event_ctx", whose members have already clearly defined which are the payloads.
I do not understand this statement at all, sorry.
> On the other hand, the purpose of the patch is to prevent the data in "struct vmci_event_ctx" from being initialized before the datagram is sent, thus preventing the uninitialized data from leaking to user space.
Great, then do this properly, again, you are just "guessing" that there
is not going to be any padding between the structures. Are you sure
there isn't? How? Where is that enforced in your patch?
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-03 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 7:10 linux-next: build failure after merge of the char-misc tree Stephen Rothwell
2025-07-03 8:30 ` Greg KH
2025-07-03 8:55 ` 回复: " Xu, Lizhi
2025-07-03 9:28 ` Greg KH
2025-07-03 9:44 ` 回复: " Xu, Lizhi
2025-07-03 10:03 ` Greg KH [this message]
2025-07-03 11:09 ` 回复: " Xu, Lizhi
2025-07-03 11:20 ` Greg KH
2025-07-04 1:32 ` Lizhi Xu
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=2025070301-albatross-angriness-00c1@gregkh \
--to=greg@kroah.com \
--cc=Lizhi.Xu@windriver.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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