Date: Wed, 22 May 2013 13:48:27 -0700
From: Andrew Morton <akpm@linux-foundation.org>
To: Joern Engel <joern@logfs.org>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
        Borislav Petkov <bp@alien8.de>, Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 06/14] bcon: add a release work struct
Message-Id: <20130522134827.2bc71496cda3e2849958c15c@linux-foundation.org>
In-Reply-To: <1368132193-25817-9-git-send-email-joern@logfs.org>
References: <1368132193-25817-1-git-send-email-joern@logfs.org>
	<1368132193-25817-9-git-send-email-joern@logfs.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 959
Lines: 19

On Thu,  9 May 2013 16:43:04 -0400 Joern Engel <joern@logfs.org> wrote:

> The final bcon_put() can be called from atomic context, by way of
> bio_endio().  In that case we would sleep in invalidate_mapping_pages(),
> with the usual unhappy results.
> 
> In nearly a year of production use, I have only seen a matching
> backtrace once.  There was a second known issue that could be reproduced
> by "yes h > /proc/sysrq-trigger" and concurrently pulling and replugging
> the blockconsole device.  It took be somewhere around 30 pulls and sore
> thumbs to reproduce and I never found the time to get to the bottom of
> it.  Quite likely the two issues are identical.

This fix should be folded into the base patch?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/