From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>,
linux-ext4@vger.kernel.org, chrubis@suse.cz
Subject: Re: OpenPosix test case mmap_11-4 fails in ext4 filesystem
Date: Wed, 21 May 2014 15:01:36 -0400 [thread overview]
Message-ID: <20140521190136.GC8868@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1405211715360.2114@localhost.localdomain>
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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-21 19:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 6:39 OpenPosix test case mmap_11-4 fails in ext4 filesystem Xiaoguang Wang
2014-05-21 12:55 ` Lukáš Czerner
2014-05-21 14:12 ` Theodore Ts'o
2014-05-21 15:06 ` chrubis
2014-05-21 18:58 ` Theodore Ts'o
2014-05-21 21:20 ` chrubis
2014-05-21 22:06 ` Eric Sandeen
2014-05-22 2:45 ` Theodore Ts'o
2014-05-22 10:45 ` chrubis
2014-05-22 14:38 ` Theodore Ts'o
2014-05-21 15:18 ` Lukáš Czerner
2014-05-21 19:01 ` Theodore Ts'o [this message]
2014-05-22 13:42 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140521190136.GC8868@thunk.org \
--to=tytso@mit.edu \
--cc=chrubis@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=wangxg.fnst@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).