From: Jordi Pujol Palomer <jordipujolp@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Miklos Szeredi <mszeredi@suse.cz>,
Vincent Batts <vbatts@gmail.com>,
David Howells <dhowells@redhat.com>,
linux-unionfs@vger.kernel.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: Overalyfs regression in 4.0
Date: Wed, 13 May 2015 20:19:36 +0200 [thread overview]
Message-ID: <20150513201936.22026b44@gmail.com> (raw)
In-Reply-To: <20150513151101.GA19583@tucsk.suse.de>
Hello,
Tested-by: Jordi Pujol Palomer <jordipujolp@gmail.com>
Have compiled the version 4.0.3 adding this patch, it works in a
Live OS,
# rmdir /mnt/
# mkdir -p /mnt
# touch /mnt/file
# rmdir /mnt/
rmdir: failed to remove ‘/mnt/’: Directory not empty
# uname -a
Linux pcjordi 4.0.3-1-haswell-lnet-amd64 #1 SMP PREEMPT Wed May 13 19:38:19 CEST 2015 x86_64 GNU/Linux
#
Thanks,
Jordi Pujol
EL Wed, 13 May 2015 17:11:01 +0200
Miklos Szeredi <miklos@szeredi.hu> escrigué:
> ---
> Subject: ovl: don't remove non-empty opaque directory
> From: Miklos Szeredi <mszeredi@suse.cz>
>
> When removing an opaque directory we can't just call rmdir() to check
> for emptyness, because the directory will need to be replaced with a
> whiteout. The replacement is done with RENAME_EXCHANGE, which doesn't
> check emptyness.
>
> Solution is just to check emptyness by reading the directory. In the
> future we could add a new rename flag to check for emptyness even for
> RENAME_EXCHANGE to optimize this case.
>
> Reported-by: Vincent Batts <vbatts@gmail.com>
> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
> Fixes: 263b4a0fee43 ("ovl: dont replace opaque dir")
> Cc: <stable@vger.kernel.org> # v4.0+
> ---
prev parent reply other threads:[~2015-05-13 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 13:06 Overalyfs regression in 4.0 Josh Boyer
2015-05-13 15:11 ` Miklos Szeredi
2015-05-13 18:19 ` Jordi Pujol Palomer [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=20150513201936.22026b44@gmail.com \
--to=jordipujolp@gmail.com \
--cc=dhowells@redhat.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@suse.cz \
--cc=vbatts@gmail.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.