linux-kernel - RE: [PATCH 37/46] Staging: hv: vmbus: Check for events before messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 31 Aug 2011 14:22:54 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Greg KH <greg@...ah.com>
CC:	"gregkh@...e.de" <gregkh@...e.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org>,
	Haiyang Zhang <haiyangz@...rosoft.com>
Subject: RE: [PATCH 37/46] Staging: hv: vmbus: Check for events before
 messages



> -----Original Message-----
> From: Greg KH [mailto:greg@...ah.com]
> Sent: Tuesday, August 30, 2011 1:38 PM
> To: KY Srinivasan
> Cc: gregkh@...e.de; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; virtualization@...ts.osdl.org; Haiyang Zhang
> Subject: Re: [PATCH 37/46] Staging: hv: vmbus: Check for events before
> messages
> 
> On Tue, Aug 30, 2011 at 05:06:39PM +0000, KY Srinivasan wrote:
> > > On Sat, Aug 27, 2011 at 11:31:36AM -0700, K. Y. Srinivasan wrote:
> > > > Conform to Windows specification by checking for events before messages.
> > >
> > > What specification?
> > >
> > > Care to provide a comment in the code that you are doing this in this
> > > explicit order because of some rule that the hypervisor imposes on us?
> >
> > I am not sure if this is documented anywhere (publicly). In talking to Windows
> > guys, they suggested this is the order in which it is done on Windows guests
> and suggested
> > I should do the same. I will see if there is some public documentation that
> specifies this.
> 
> All you need to do is just document it in the code and I'll be happy.
> We don't rely on external documentation for things to be changed, in
> fact, there usually isn't any such thing :)

Ok; will do.

Regards,

K. Y

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/