linux-ext4 - Re: linux-2.6-block/for-next: Removal of BLKDEV_IFL_BARRIER and BLKDEV_IFL

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: <4CBBF382.4000505@kernel.dk>
Date:	Mon, 18 Oct 2010 09:13:06 +0200
From:	Jens Axboe <axboe@...nel.dk>
To:	sedat.dilek@...il.com
CC:	Sedat Dilek <sedat.dilek@...glemail.com>,
	linux-ext4@...r.kernel.org, Theodore Ts'o <tytso@....edu>
Subject: Re: linux-2.6-block/for-next: Removal of BLKDEV_IFL_BARRIER and BLKDEV_IFL_WAIT

On 2010-10-18 02:11, Sedat Dilek wrote:
> Hi,
> 
> today, I pulled linux-2.6-block/for-next GIT branch [1] on top of
> Linus-tree (2.6.36-rc8-git3).
> 
> Unfortunately, ext4/next GIT branch [2] is not "GIT-pull-able" on top
> of this local GIT repository.
> The cause for this is the removal of BLKDEV_IFL_BARRIER and
> BLKDEV_IFL_WAIT in linux-2.6-block/for-next.
> 
> As there are few days left for 2.6.36-final, it would be great when
> ext4/next could be prepared to work with linux-2.6-block/for-next.
> Thanks in advance.

The argument just has to be removed. linux-next has had a fixup
patch for this for a long time.

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html