From: Harshavardhana <harsha@gluster.com>
To: kreijack@libero.it
Cc: Goffredo Baroncelli <kreijack@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH][TAKE-1] fs/btrfs: Return EPERM for rmdir on subvolumes and snapshots
Date: Fri, 09 Apr 2010 14:13:07 -0700 [thread overview]
Message-ID: <4BBF9863.50504@gluster.com> (raw)
In-Reply-To: <4BBF970E.7000903@gluster.com>
On 04/09/2010 02:07 PM, Harshavardhana wrote:
> EBUSY is again meant for different reason where in a super block is
> being locked or accessed by an Application which would mean unref on
> that block would cause Application to go nuts. In such cases EBUSY is
> returned.
Ok i think ENOTSUPP could be another alternative? . This should be ok i
guess?
Regards
--
Harshavardhana
http://www.gluster.com
next prev parent reply other threads:[~2010-04-09 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 22:47 [PATCH][TAKE-1] fs/btrfs: Return EPERM for rmdir on subvolumes and snapshots Harshavardhana
2010-04-09 17:58 ` Goffredo Baroncelli
2010-04-09 18:39 ` Harshavardhana
2010-04-09 18:54 ` Goffredo Baroncelli
2010-04-09 21:07 ` Harshavardhana
2010-04-09 21:13 ` Harshavardhana [this message]
2010-04-09 21:42 ` Goffredo Baroncelli
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=4BBF9863.50504@gluster.com \
--to=harsha@gluster.com \
--cc=kreijack@gmail.com \
--cc=kreijack@libero.it \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).