linux-ext4 - Re: OpenPosix test case mmap_11-4 fails in ext4 filesystem

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: <20140521190136.GC8868@thunk.org>
Date:	Wed, 21 May 2014 15:01:36 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Lukáš Czerner <lczerner@...hat.com>
Cc:	Xiaoguang Wang <wangxg.fnst@...fujitsu.com>,
	linux-ext4@...r.kernel.org, chrubis@...e.cz
Subject: Re: OpenPosix test case mmap_11-4 fails in ext4 filesystem

On Wed, May 21, 2014 at 05:18:24PM +0200, Lukáš Czerner wrote:
> 
> I am not disputing it, but since he seems to be using RHEL I am
> asking for the triage with Red Hat support.

Sure, it makes sence that a RH bugzilla entry be opened to make sure
that whatever eventual bug fix we have in upstream gets backported to
the RHEL 7.0RC kernel.

And sure, normally when someone uses distro-specific version
references when reporting bugs upstream, this is not the best
procedure, especially since not everyone (including me) has access to
RHEL 7.0 RC kernels.  However, I'm minded to overlook such faux pas
when the bug report is accompanied by a very nice test case which
makes it trivial to verify the problematic behavior, and that the
problem is present upstream.

Cheers,

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