linux-kernel - Re: [GIT PULL] block bits for 3.1-rc

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]

Date:	Sun, 21 Aug 2011 20:37:11 +0200
From:	Jens Axboe <jaxboe@...ionio.com>
To:	Christoph Hellwig <hch@...radead.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] block bits for 3.1-rc

On 2011-08-21 20:19, Christoph Hellwig wrote:
> On Sun, Aug 21, 2011 at 07:56:17PM +0200, Jens Axboe wrote:
>> The discussion was on lkml, as Mike points out. But yes, short time to
>> react. Since I can't easily cater to both cases right now, how about we
>> add a temporary second meta flag that is only used for tracing?
>>
>>         REQ_META        = (__REQ_META | __REQ_META_TRACE),
>>         RET_META_TRACE  = __REQ_META_TRACE,
>>
>> You get the idea. Not super pretty, but it should solve the immediate
>> issue.
> 
> I'd do it the other way around and add a new REQ_META_BOOST flag to
> the old callers.  I'll cook up a patch on the airport / on my flight
> if you want.

That would work fine as well, please do cook up the patch if you have
flight time anyway :-)

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