All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [patch] handle race to mkdir at startup
Date: Fri, 17 Apr 2009 06:49:51 +0000	[thread overview]
Message-ID: <20090417064951.GI4593@kernel.dk> (raw)
In-Reply-To: <x49y6u01l1c.fsf@segfault.boston.devel.redhat.com>

On Thu, Apr 16 2009, Jeff Moyer wrote:
> Hi,
> 
> I ran into a problem when specifying -D dirname-that-doesnt-yet-exist.
> Blktrace would fail, spewing the following messages:
> 
> [root@megadeth blktrace]# ./blktrace -d /dev/cciss/c0d1 -D ./2.6.30-rc2-cfq-local
> Destination dir ./2.6.30-rc2-cfq-local/ can't be made: 17/File exists
> Destination dir ./2.6.30-rc2-cfq-local/ can't be made: 17/File exists
> Destination dir ./2.6.30-rc2-cfq-local/ can't be made: 17/File exists
> Destination dir ./2.6.30-rc2-cfq-local/ can't be made: 17/File exists
> Destination dir ./2.6.30-rc2-cfq-local/ can't be made: 17/File exists
> FAILED to start thread on CPU 0: 1/Operation not permitted
> FAILED to start thread on CPU 4: 1/Operation not permitted
> FAILED to start thread on CPU 5: 1/Operation not permitted
> FAILED to start thread on CPU 6: 1/Operation not permitted
> FAILED to start thread on CPU 7: 1/Operation not permitted
> 
> I tracked it down to the fact that there is no synchronization between
> threads when trying to create the output directory.  The fix is simple,
> just allow the race to happen and detect it.  It's not really worth
> putting in any extra synchronization.  It looks like no place else in
> that startup path needs synchronization either.
> 
> This patch fixes the issue for me.  I tested it by running the very
> command that caused me headaches 100% of the time before.  I also did a
> chattr +i on the directory and verified that it would really fail in the
> case where it couldn't create the directory.
> 
> Cheers,
> Jeff
> 
> diff --git a/blktrace.c b/blktrace.c
> index 656ab7a..b4c919d 100644
> --- a/blktrace.c
> +++ b/blktrace.c
> @@ -1477,7 +1477,12 @@ static int fill_ofname(struct io_info *iop, int cpu)
>  				iop->ofn, errno, strerror(errno));
>  			return 1;
>  		}
> -		if (mkdir(iop->ofn, 0755) < 0) {
> +		/*
> +		 * There is no synchronization between multiple threads
> +		 * trying to create the directory at once.  It's harmless
> +		 * to let them try, so just detect the problem and move on.
> +		 */
> +		if (mkdir(iop->ofn, 0755) < 0 && errno != EEXIST) {
>  			fprintf(stderr,
>  				"Destination dir %s can't be made: %d/%s\n",
>  				iop->ofn, errno, strerror(errno));

Thanks Jeff, applied!

-- 
Jens Axboe


      reply	other threads:[~2009-04-17  6:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 19:00 [patch] handle race to mkdir at startup Jeff Moyer
2009-04-17  6:49 ` Jens Axboe [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=20090417064951.GI4593@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-btrace@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 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.