linux-kernel - Re: [GIT PULL] Two fixups for the block IO merge

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1301072954-sup-4222@think>
Date:	Fri, 25 Mar 2011 13:09:52 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	Jens Axboe <jaxboe@...ionio.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Two fixups for the block IO merge

Excerpts from Jens Axboe's message of 2011-03-25 12:07:07 -0400:
> Hi Linus,
> 
> An embarassing bug made the block IO merge a bit less enjoyable for some
> people than it should have.
> 
> - The oops problem (with CFQ), or potential corruption (with noop) due
>   to a bad insertion type for some requests.
> 
> - A warning spew on virt_io using blk_stop_queue() inside it's callback.
> 
> Please pull these two fixes, so hopefully we can put this behind us.
> Thanks a lot to the people involved with fixing the first issue.
> 
>   git://git.kernel.dk/linux-2.6-block.git for-linus
> 
> Jens Axboe (2):
>       block: fix bug with inserting flush requests as sort/merge
>       block: fix issue with calling blk_stop_queue() from the request_fn handler

A quick stress test on this is going well on my box.  Before this pull
it would crash within 5 minutes.

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