linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Josef Bacik <jbacik@fb.com>
Cc: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
	Brian Foster <bfoster@redhat.com>,
	fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] generic/311: Disable dmesg check
Date: Thu, 23 Jul 2015 07:10:50 +1000	[thread overview]
Message-ID: <20150722211050.GZ3902@dastard> (raw)
In-Reply-To: <55AF7E77.5020803@fb.com>

On Wed, Jul 22, 2015 at 07:28:55AM -0400, Josef Bacik wrote:
> On 07/22/2015 01:27 AM, Dave Chinner wrote:
> >>>Josef, Chris, is this really how btrfs handles metadata write
> >>>failures? This handling of errors seems like a design flaw rather
> >>>than a desireable behaviour to me....
> >>>
> >>
> >>Jeeze you are cranky Dave, lets think about what this test is doing.
> >
> >Do you really see anything above that indicates I'm cranky? I'm just
> >following the logic as i read it, reaching a conclusion and the
> >saying "this doesn't sound right - can an expert please confirm I've
> >got this right?".  Last thing I expected was to be shouted at and
> >treated like an idiot.
> >
> >BTW, you'll know when I'm cranky - swearing is a real good
> >indication that I'm pissed off at something or someone.
> 
> Sorry, I didn't mean to come across angry or condescending.
> Obviously I appreciate your expertise and questions, I wasn't pissed
> or anything, this is just how I normally talk, you know I use
> swearing as punctuation.

Yes, I know that, and that doesn't worry me in the least.

You don't normally shout, though.

> >>This is part of the reason for dm-log-writes, to solve this kind of
> >>shitty situation that dm-flakey introduces.
> >
> >Which you've also never explained in any of the dm-log-write patches
> >you've posted in the past.  IOWs, get the dm-log-writes support code
> >reviewed and fix the dm-flakey tests to use it so this problem goes
> >away.
> 
> The dm-log-writes target is already upstream, I sent the xfstests
> stuff months ago, not sure if they ever made it in.  I'll check and
> get them posted again if not.  Thanks,

They didn't, because it wasn't clear when the kernel code was going
to be committed. I did notice yesterday that it was upstream.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2015-07-22 21:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  4:56 [PATCH] generic/311: Disable dmesg check Chandan Rajendra
2015-07-17 10:16 ` Brian Foster
2015-07-17 11:40   ` Chandan Rajendra
2015-07-19 23:54     ` Dave Chinner
2015-07-20 12:55       ` Josef Bacik
2015-07-20 22:12         ` Dave Chinner
2015-07-21 10:33           ` Chandan Rajendra
2015-07-22  0:01             ` Dave Chinner
2015-07-22  0:37               ` Josef Bacik
2015-07-22  5:27                 ` Dave Chinner
2015-07-22 11:28                   ` Josef Bacik
2015-07-22 21:10                     ` Dave Chinner [this message]
2015-07-22 12:47                   ` Josef Bacik
2015-07-22 23:02                     ` Dave Chinner
2017-02-20 15:03 ` Anand Jain
2017-02-22  9:32   ` Chandan Rajendra
2017-02-23  6:40     ` Anand Jain

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=20150722211050.GZ3902@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=chandan@linux.vnet.ibm.com \
    --cc=fstests@vger.kernel.org \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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).