[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140827092002.GA1827@sucs.org>
Date: Wed, 27 Aug 2014 10:20:02 +0100
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 0/4] Drivers: hv: vmbus: Eliminate calls to BUG_ON()
On Tue, Aug 26, 2014 at 12:05:22PM -0700, K. Y. Srinivasan wrote:
> Cleanup the channel management code and eliminate calls to BUG_ON()
>
> K. Y. Srinivasan (4):
> Drivers: hv: vmbus: Cleanup vmbus_post_msg()
> Drivers: hv: vmbus: Cleanup vmbus_teardown_gpadl()
> Drivers: hv: vmbus: Cleanup vmbus_close_internal()
> Drivers: hv: vmbus: Cleanup vmbus_establish_gpadl()
I've applied these on top of 3.17-rc1 and my Hyper-V guest with most
verification on bar DEBUG_PAGEALLOC boots without issue so long as I
have more than one CPU assigned (that issue is being investigated in
https://lkml.org/lkml/2014/8/26/271, [PANIC, hyperv] BUG: unable to
handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)).
With DEBUG_PAGEALLOC on I hit https://lkml.org/lkml/2014/8/19/227 (BUG:
unable to handle kernel paging request at ffff8801f3febe63
(netvsc_select_queue)) but that's different to the above BUG_ONs.
--
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/
Powered by blists - more mailing lists