linux-kernel - Re: [PATCH v4 1/9] VMware balloon: partially inline vmballoon_reserve

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:	Thu, 6 Aug 2015 14:07:55 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	"Philip P. Moltmann" <moltmann@...are.com>
Cc:	Xavier Deguillard <xdeguillard@...are.com>,
	dmitry.torokhov@...il.com, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, pv-drivers@...are.com
Subject: Re: [PATCH v4 1/9] VMware balloon: partially inline
 vmballoon_reserve_page.

On Thu, Aug 06, 2015 at 01:33:39PM -0700, Philip P. Moltmann wrote:
> From: Xavier Deguillard <xdeguillard@...are.com>
> 
> This split the function in two: the allocation part is inlined into the
> inflate function and the lock part is kept into his own function.
> 
> This change is needed in order to be able to allocate more than one page
> before doing the hypervisor call.
> 
> Signed-off-by: Xavier Deguillard <xdeguillard@...are.com>
> Acked-by: Dmitry Torokhov <dtor@...are.com>
> Signed-off-by: Philip P. Moltmann <moltmann@...are.com>
> Acked-by: Andy King <acking@...are.com>
> ---
>  drivers/misc/vmw_balloon.c | 98 ++++++++++++++++++++--------------------------
>  1 file changed, 42 insertions(+), 56 deletions(-)

This fails to apply on my tree, so I can't apply this series at all :(

Please rebase on char-misc-next and resend them so that I can apply
them.  This shows you didn't even test this series in any form, which
does not make me feel like it's worth accepting, don't you agree?

greg k-h
--
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/