All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Jordi Pujol <jordipujolp@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: overlayfs patches for ovl_copy_up & ovl_rename
Date: Wed, 18 May 2011 10:42:53 +0200	[thread overview]
Message-ID: <87zkmkmmb6.fsf@tucsk.pomaz.szeredi.hu> (raw)
In-Reply-To: <201105180944.35027.jordipujolp@gmail.com> (Jordi Pujol's message of "Wed, 18 May 2011 09:44:34 +0200")

Jordi Pujol <jordipujolp@gmail.com> writes:

> A Dimarts 17 Maig 2011 20:07:13, vàreu escriure:
>> Jordi, what about the original bug you reported:
>> >>>- a few days ago we talked about an error when repetitive sed
>> >>>instructions were executed, also it happens in other processes,
>> >>>like mantaining list of installed files for actual packages, that
>> >>>is solved in ovl_rename issuing a dget for the old-dentry and
>> >>>parent dentries. (This code is inspired on rename.c from unionfs)
>> 
>> Is this still happening?  Does the debug patch make any difference?
>
> my patch adds some dget/dput operations that minimize the problem, it
> occurs less times, but it happens.  I suppose that those extra
> operations add an execution delay before processing the main routine;

Probably timing related, yes.

> a deduction is that locking dentries is required to synchronize a rename to 
> not be executed until another rename operation has finished.

Already done by the VFS.  The locks used actually provide stronger
guarantees than your code.  See

  Documentation/filesystems/directory-locking

for all the gory details.

So, is there a minimal test case that I can try to replicate the bad
behavior?

Thanks,
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-05-18  8:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 14:59 overlayfs patches for ovl_copy_up & ovl_rename Jordi Pujol
2011-05-05  9:06 ` Miklos Szeredi
2011-05-09  6:38   ` Jordi Pujol
2011-05-10 16:20     ` Miklos Szeredi
2011-05-17  8:43       ` Miklos Szeredi
2011-05-17 17:18         ` Jordi Pujol
2011-05-17 18:07           ` Miklos Szeredi
2011-05-18  7:44             ` Jordi Pujol
2011-05-18  8:42               ` Miklos Szeredi [this message]
2011-05-19  7:47                 ` Jordi Pujol
2011-05-19  8:49                   ` Miklos Szeredi
2011-05-19  9:24                     ` Jordi Pujol
2011-05-19  9:52                       ` Miklos Szeredi
2011-05-19 13:34                         ` Jordi Pujol
2011-05-21  5:10                       ` Jordi Pujol
2011-05-23  9:21                         ` Miklos Szeredi
2011-05-24 15:53                           ` Jordi Pujol
2011-05-27 15:03                           ` Jordi Pujol
2011-05-31  9:01                             ` Miklos Szeredi
2011-05-19  8:52                   ` Jordi Pujol

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=87zkmkmmb6.fsf@tucsk.pomaz.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=jordipujolp@gmail.com \
    --cc=linux-fsdevel@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.