All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: xfs mailing list <xfs@oss.sgi.com>
Cc: Lachlan McIlroy <lmcilroy@redhat.com>
Subject: [PATCH] xfstests 246: Test for race between direct I/O and mmap
Date: Fri, 12 Nov 2010 16:37:07 -0600	[thread overview]
Message-ID: <4CDDC193.9030208@redhat.com> (raw)



From: Lachlan McIlroy <lmcilory@redhat.com>

A customer reported a problem:

If a process is using mmap to write to a file on an 
ext4 filesystem while another process is using direct 
I/O to write to the same file the first thread may 
receive a SIGBUS during a page fault.

A SIGBUS occurs if the page fault tries to access a 
page that is entirely beyond the end of the file but 
in this test case that should not be happening.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---

#! /bin/bash
# FS QA Test No. 246
#
# Test for race between direct I/O and mmap
#
#-----------------------------------------------------------------------
# Copyright (c) 2010 Red Hat, Inc.  All Rights Reserved.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License as
# published by the Free Software Foundation.
#
# This program is distributed in the hope that it would be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write the Free Software Foundation,
# Inc.,  51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
#-----------------------------------------------------------------------
#
# creator
owner=lmcilroy@redhat.com

seq=`basename $0`
echo "QA output created by $seq"

here=`pwd`
tmp=/tmp/$$
status=1	# failure is the default!
trap "_cleanup; exit \$status" 0 1 2 3 7 15

_cleanup()
{
    cd /
    rm -f $tmp.* $testfile
    wait
}

# get standard environment, filters and checks
. ./common.rc
. ./common.filter

# real QA test starts here

# Modify as appropriate.
_supported_fs generic
_supported_os Linux

testfile=$TEST_DIR/$seq.$$

loops=500
iosize=1048576

# Initialise file
dd if=/dev/zero of=$testfile bs=$iosize count=$loops &> /dev/null
[ $? -ne 0 ] && exit
sync
	
# Direct I/O overwriter
dd if=/dev/zero of=$testfile oflag=direct bs=$iosize count=$loops conv=notrunc &> /dev/null &
[ $? -ne 0 ] && exit

# Mmap writer
start=`expr $loops - 1`
for i in `seq $start -1 0`
do
	offset=`expr $i \* $iosize`
	$XFS_IO_PROG -F -f -c "mmap -w $offset $iosize" -c "mwrite $offset $iosize" $testfile
	[ $? -ne 0 ] && exit
done

wait

echo "Silence is golden."

# success, all done
status=0
exit


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2010-11-12 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 22:37 Eric Sandeen [this message]
2010-11-15  1:01 ` [PATCH] xfstests 246: Test for race between direct I/O and mmap Lachlan McIlroy
2010-11-15  3:57   ` Eric Sandeen
2010-11-18  5:36 ` Dave Chinner

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=4CDDC193.9030208@redhat.com \
    --to=sandeen@redhat.com \
    --cc=lmcilroy@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.