linux-kernel - Re: [PATCH 3/3] Drivers: hv: hv_balloon: Don't post pressure status from interrupt context

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]

Message-ID: <20141207080433.GA4531@sucs.org>
Date:	Sun, 7 Dec 2014 08:04:34 +0000
From:	Sitsofe Wheeler <sitsofe@...il.com>
To:	"K. Y. Srinivasan" <kys@...rosoft.com>
Cc:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
	jasowang@...hat.com
Subject: Re: [PATCH 3/3] Drivers: hv: hv_balloon: Don't post pressure status
 from interrupt context

On Tue, Dec 02, 2014 at 02:29:15PM -0800, K. Y. Srinivasan wrote:
> We currently release memory (balloon down) in the interrupt context and we also
> post memory status while releasing memory. Rather than posting the status
> in the interrupt context, wakeup the status posting thread to post the status.
> This will address the inconsistent lock state that Sitsofe Wheeler <sitsofe@...il.com>
> reported:

Sorry I didn't follow up on this. Things looked better after the patch
but I was seeing a strange issue where the memory was being reduced to
some minimum and the balloon would never shrink so the available memory
was seemingly locked from then on. I ran out of time to investigate this
later behaviour and didn't have the time to check if it had always been
the case but I think I see other patches saying you nailed it and other
issues. Do you have a published git tree with all these pieces in or
have they already been mainlined?

-- 
Sitsofe | http://sucs.org/~sits/
--
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/