linux-kernel - Re: [PATCH V2] umem: fix up unplugging

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: <20120613191801.GC8230@kernel.dk>
Date:	Wed, 13 Jun 2012 21:18:01 +0200
From:	Jens Axboe <jaxboe@...ionio.com>
To:	Tao Guo <glorioustao@...il.com>
Cc:	linux-kernel@...r.kernel.org, Tao Guo <Tao.Guo@....com>,
	Neil Brown <neilb@...e.de>, Shaohua Li <shli@...nel.org>,
	stable@...r.kernel.org
Subject: Re: [PATCH V2] umem: fix up unplugging

On Thu, Jun 07 2012, Tao Guo wrote:
> Fix a regression introduced by 7eaceaccab5f40 ("block: remove per-queue
> plugging").  In that patch, Jens removed the whole mm_unplug_device()
> function, which used to be the trigger to make umem start to work.
> 
> We need to implement unplugging to make umem start to work, or I/O will
> never be triggered.

Applied this one, dropped the other two. Would still be nice to move
this generic functionality into the block core and unify md/umem in this
regard for 3.6, if you would like to do that.

-- 
Jens Axboe

--
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/