From: Mark Fasheh <mfasheh@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: check if cluster name exists before deref
Date: Wed, 26 Mar 2014 15:23:57 -0700 [thread overview]
Message-ID: <20140326222357.GF5716@wotan.suse.de> (raw)
In-Reply-To: <20140326150840.6025512719ffbc4a601dd808@linux-foundation.org>
On Wed, Mar 26, 2014 at 03:08:40PM -0700, Andrew Morton wrote:
> On Wed, 26 Mar 2014 15:00:18 -0700 Mark Fasheh <mfasheh@suse.de> wrote:
>
> > > As a side note, how the hell was this new code path tested?
> > > It's obviously broken and there's no way it even passes
> > > a very basic test.
> >
> > I'm not trying to 'defend' Goldwyn, or anything, but mistakes get made -
> > it's a fact of life. We have a review process to hopefully catch these sorts
> > of things, you are welcome to take part in it. In fact, if you were
> > willing to test and report these sorts of things to the Ocfs2-devel list
> > before they go upstream that would probably help prevent this sort of thing
> > from happening in the future.
>
> Well. Sasha is the kernel's reigning testing-and-reporting champion. On
> linux-next, no less.
Huh, Sasha, are you testing Ocfs2 from linux-next? If so some details of how
/ what you test would be appreciated. Otherwise, perhaps we could talk
about some basic Ocfs2 tests then?
> What concerns me is that the wrong patch version was merged, or it got
> mangled in flight somehow.
I kind of assumed that must've been what happened, but probably on
Goldwyn's end - that he sent the wrong version of the patch or something.
It's not like that hasn't happened to me before, etc. In flight would be
weird for me to hear though, I've never experienced that happening.
--Mark
--
Mark Fasheh
next prev parent reply other threads:[~2014-03-26 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 17:21 [Ocfs2-devel] [PATCH] ocfs2: check if cluster name exists before deref Sasha Levin
2014-03-26 21:33 ` Andrew Morton
2014-03-26 21:43 ` Mark Fasheh
2014-03-26 22:00 ` Mark Fasheh
2014-03-26 22:08 ` Andrew Morton
2014-03-26 22:23 ` Mark Fasheh [this message]
2014-03-26 22:23 ` Sasha Levin
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=20140326222357.GF5716@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=ocfs2-devel@oss.oracle.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).