linux-kernel - fix queue_lock usage in blk-mq and nvme

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-next>] [day] [month] [year] [list]

Message-Id: <1430984294-25859-1-git-send-email-hch@lst.de>
Date:	Thu,  7 May 2015 09:38:12 +0200
From:	Christoph Hellwig <hch@....de>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: fix queue_lock usage in blk-mq and nvme

Historically we always take queue_lock with irqs disabled.  Blk-mq doesn't really
use the queue_lock much, but when it does it needs to follow this rules to make
lockdep happy.

The first patch removes a queue_lock usage instead of fixing things properly,
and the second is a bad-aid for nvme.  In the long run I'd prefer to remove
other users of the queue_lock from blk-mq and blk-mq based driver entirely,
but that will require a bit more work.

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