linux-kernel - Re: [PATCH] bcache: bch_writeback

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: <alpine.LNX.2.00.1605240103090.31937@cbobk.fhfr.pm>
Date:	Tue, 24 May 2016 01:05:42 +0200 (CEST)
From:	Jiri Kosina <jikos@...nel.org>
To:	Kent Overstreet <kent.overstreet@...il.com>
cc:	linux-bcache@...r.kernel.org, linux-kernel@...r.kernel.org,
	Eric Wheeler <bcache@...ts.ewheeler.net>,
	Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH] bcache: bch_writeback_thread() is not freezable

On Wed, 18 May 2016, Jiri Kosina wrote:

> > > bch_writeback_thread() is calling try_to_freeze(), but that's just an 
> > > expensive no-op given the fact that the thread is not marked freezable.
> > > 
> > > I/O helper kthreads, exactly such as the bcache writeback thread, actually 
> > > shouldn't be freezable, because they are potentially necessary for 
> > > finalizing the image write-out.
> > > 
> > > Signed-off-by: Jiri Kosina <jkosina@...e.cz>
> > 
> > Let's send a friendly ping on these three patches after two weeks...
> 
> After a month, I think, it's time for another ping.

[ adding Jens to CC ]

Ok, I call it officially ridiculous now. I guess I'll be resending through 
akpm.

Is it a time to claim (by MAINTAINERS entry) the in-tree bcache orphaned?

-- 
Jiri Kosina
SUSE Labs