linux-ext4 - Re: [PATCH] libext2fs: fix return value

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:	Sat, 4 May 2013 20:40:21 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Mike Frysinger <vapier@...too.org>
Cc:	Theodore Ts'o <tytso@....edu>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] libext2fs: fix return value

On 2013-05-04, at 18:58, Mike Frysinger <vapier@...too.org> wrote:
> On Saturday 04 May 2013 19:55:03 Theodore Ts'o wrote:
>> On Sat, May 04, 2013 at 01:05:54AM -0400, Mike Frysinger wrote:
>>> The ext2fs_test_block_bitmap_range2 func is not a void, so make sure we
>>> return a value.  I picked EINVAL as it looks like what other things in
>>> this func use.
>>> 
>>> URL: http://bugs.gentoo.org/467986
>>> Reported-by: Vicente Olivert Riera <vincent@...too.org>
>>> Signed-off-by: Mike Frysinger <vapier@...too.org>
>> 
>> This is already fixed in e2fsprogs's git repository, in commit
>> 0d89e5acea9.
> 
> ok, the use of "master" and "next" is weird.  i was using the normal "master" 
> branch which is apparently out of date.

I'd have to agree. It would be great if master was merged from maint more often so that patches would apply to either.

Cheers, Andreas--
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