From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfsqa: add delayed allocation @ ENOSPC exerciser
Date: Thu, 4 Mar 2010 02:57:53 -0500 [thread overview]
Message-ID: <20100304075753.GA16740@infradead.org> (raw)
In-Reply-To: <20100303223122.GA14317@discord.disaster>
On Thu, Mar 04, 2010 at 09:31:22AM +1100, Dave Chinner wrote:
> On Wed, Mar 03, 2010 at 07:56:19AM -0500, Christoph Hellwig wrote:
> > On Wed, Mar 03, 2010 at 05:19:20PM +1100, Dave Chinner wrote:
> > > + killall -9 dd > /dev/null 2>&1
> >
> > This seems a bit dangerous. I have at least one old system that
> > uses dd to continously read the kernel message buffer in the
> > background, and there's tons of other potential dd uses.
>
> I only put it there to make sure they all died when I ^C'd out of a
> test run while testing the test. I forgot to remove it - I'll drop
> it from the patch.
Ok with that change. Although beeing able to Ctrl+C testcase is a nice
gimmick to have.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-03-04 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 6:19 [PATCH 0/3] xfsqa: new tests and fixes Dave Chinner
2010-03-03 6:19 ` [PATCH 1/3] xfsqa: add delayed allocation @ ENOSPC exerciser Dave Chinner
2010-03-03 12:56 ` Christoph Hellwig
2010-03-03 22:31 ` Dave Chinner
2010-03-04 7:57 ` Christoph Hellwig [this message]
2010-03-03 6:19 ` [PATCH 2/3] xfsqa: fix size specification for scratch mkfs Dave Chinner
2010-03-03 12:58 ` Christoph Hellwig
2010-03-03 16:21 ` Eric Sandeen
2010-03-03 22:56 ` Dave Chinner
2010-03-03 6:19 ` [PATCH 3/3] xfsqa: Add fiemap exerciser Dave Chinner
2010-03-03 12:58 ` Christoph Hellwig
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=20100304075753.GA16740@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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