ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: check if cluster name exists before deref
Date: Wed, 26 Mar 2014 18:23:41 -0400	[thread overview]
Message-ID: <5333536D.5020603@oracle.com> (raw)
In-Reply-To: <20140326220018.GE5716@wotan.suse.de>

On 03/26/2014 06:00 PM, Mark Fasheh wrote:
> On Tue, Mar 25, 2014 at 01:21:58PM -0400, Sasha Levin 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.

Hi Mark,

I'm fuzz testing the kernel and not really testing or reviewing any subsystem
in particular.

My frustration about not testing it was because it's so simple to reproduce this
issue:

  # mount -t ocfs2_dlmfs ocfs2_dlmfs dlm
  # mkdir dlm/anything
  [ boom ]

This is a very basic test that should have been run more than once before this
patch made it into Linus's tree. Whether as part of some ocfs2 test suite or
maybe xfstest.

My beef is not with Goldwyn not testing that path, it's more with whatever
process (or lack thereof) ocfs2 has to test and verify patches before
they make it upstream. Even if Goldwyn missed it, it should have been
caught at a different place on it's way.


Thanks,
Sasha

      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
2014-03-26 22:23   ` Sasha Levin [this message]

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=5333536D.5020603@oracle.com \
    --to=sasha.levin@oracle.com \
    --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).