From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Tom Zanussi <zanussi@comcast.net>
Cc: jens.axboe@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] relay: move remove_buf_file inside relay_close_buf
Date: Tue, 06 Apr 2010 13:34:33 +0400 [thread overview]
Message-ID: <87hbnox6ty.fsf@openvz.org> (raw)
In-Reply-To: <1267292137-12930-1-git-send-email-dmonakhov@openvz.org> (Dmitry Monakhov's message of "Sat, 27 Feb 2010 20:35:37 +0300")
add Tom Zanussi to recipients.
Tom, please take a look at the patch, it is simple and clean and it able
to solve long standing blktrace related bug.
Dmitry Monakhov <dmonakhov@openvz.org> writes:
> Currently remove_buf_file callback is called from from kobject
> release method. This result in follow issue:
> # blktrace -d /dev/sda1 -d /dev/sda -o test
> blktrace_setup()
> dir = create_dir()
> rchan = relay_open(dir,...)
> ->create_buf_file_callback
> buf_file = debugfs_create_file(dir, )
>
> Userspace will open buf_file.
> Later we make a decision to stop tracing
> blktrace_down()
> relay_close(rhcan) /* just decrement kobj reference */
> /* since it is not zero then callback not called */
> debugfs_remove(dir) /* FAIL due to non empty dir */
>
> Later user space will close the file and file will be deleted,
> but directory still exist.
> user_space_close()
> ->file_release
> ->release_buf_file_callback
> ->debugfs_remove(buf_file)
>
> In fact this is general issue, blktrace is just one of examples.
> We can not reliably remove parent dir until all users close the
> buf_file.
>
> We don't have to wait this long. File may be deleted
> inside relay_close_buf().
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> ---
> kernel/relay.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/relay.c b/kernel/relay.c
> index c705a41..dcf71c8 100644
> --- a/kernel/relay.c
> +++ b/kernel/relay.c
> @@ -237,7 +237,6 @@ static void relay_destroy_buf(struct rchan_buf *buf)
> static void relay_remove_buf(struct kref *kref)
> {
> struct rchan_buf *buf = container_of(kref, struct rchan_buf, kref);
> - buf->chan->cb->remove_buf_file(buf->dentry);
> relay_destroy_buf(buf);
> }
>
> @@ -487,6 +486,7 @@ static void relay_close_buf(struct rchan_buf *buf)
> {
> buf->finalized = 1;
> del_timer_sync(&buf->timer);
> + buf->chan->cb->remove_buf_file(buf->dentry);
> kref_put(&buf->kref, relay_remove_buf);
> }
next prev parent reply other threads:[~2010-04-06 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 17:35 [PATCH] relay: move remove_buf_file inside relay_close_buf Dmitry Monakhov
2010-02-28 18:48 ` Jens Axboe
2010-04-06 9:34 ` Dmitry Monakhov [this message]
2010-04-07 5:24 ` Tom Zanussi
-- strict thread matches above, loose matches on Subject: below --
2013-04-22 7:57 Dmitry Monakhov
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=87hbnox6ty.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@comcast.net \
/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.