linux-kernel - Re: [PATCH 06/14] bcon: add a release work struct

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: <20130522134827.2bc71496cda3e2849958c15c@linux-foundation.org>
Date:	Wed, 22 May 2013 13:48:27 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Joern Engel <joern@...fs.org>
Cc:	linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
	Borislav Petkov <bp@...en8.de>, Takashi Iwai <tiwai@...e.de>
Subject: Re: [PATCH 06/14] bcon: add a release work struct

On Thu,  9 May 2013 16:43:04 -0400 Joern Engel <joern@...fs.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/