linux-kernel - Re: block: fully initialize queue in blk_mq_init_allocated

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: <20150313123709.GA430@swordfish>
Date:	Fri, 13 Mar 2015 21:37:10 +0900
From:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:	Mike Snitzer <snitzer@...hat.com>
Cc:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
	Ming Lei <ming.lei@...onical.com>,
	Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org
Subject: Re: block: fully initialize queue in blk_mq_init_allocated_queue

On (03/13/15 08:24), Mike Snitzer wrote:
> Thanks, but I already fixed these 2 patches and pushed them to
> linux-dm.git's for-next branch last night (I also posted v3 of the
> corresponding patches to LKML at that time).

oh, I see. didn't know that.

> Sorry to waste your time, I've learned my lesson:
> 

no problem.

> Hopefully linux-next was able to pick up my new 'for-next' and we don't
> have an entire weekend of linux-next crashes due to my idiocy.

nope, this is how I spot it -- next-20150313 doesn't boot.

thanks,

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