linux-kernel - Re: [GIT PULL] Block driver changes for 3.20

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: <54DD3017.7030909@fb.com>
Date:	Thu, 12 Feb 2015 15:58:31 -0700
From:	Jens Axboe <axboe@...com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Tejun Heo <tj@...nel.org>,
	Ronny Hegewald <Ronny.Hegewald@...ine.de>,
	Dan Williams <dan.j.williams@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Block driver changes for 3.20

On 02/12/2015 03:55 PM, Linus Torvalds wrote:
> On Thu, Feb 12, 2015 at 2:50 PM, Jens Axboe <axboe@...com> wrote:
>>
>> When the code was moved, it also morphed into the sas specific tag
>> allocation. And the LOWTAG part was for sil24, which doesn't call that code
>> anymore.
>
> Hmm. So where does the sil24 get its tag allocation from then? Because
> then *that* code presumably needs the LOWTAG hackery..


commit 9269e23496ddd83b974536019cf420520df0ee7f
Author: Shaohua Li <shli@...com>
Date:   Fri Jan 23 20:17:59 2015 -0800

     libata: make sata_sil24 use fifo tag allocator

     libata starts using block tag now, we can use BLK_TAG_ALLOC_FIFO to
     solve the sata_sil24 tag bug.

     https://bugzilla.kernel.org/show_bug.cgi?id=87101

     Cc: Christoph Hellwig <hch@...radead.org>
     Signed-off-by: Shaohua Li <shli@...com>
     Acked-by: Tejun Heo <tj@...nel.org>
     Acked-by: Dan Williams <dan.j.williams@...el.com>
     Signed-off-by: Jens Axboe <axboe@...com>


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