From: Goffredo Baroncelli <kreijack@libero.it>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V2] Removing a subvolume by an ordinary user
Date: Sun, 17 Oct 2010 17:53:44 +0200 [thread overview]
Message-ID: <201010171753.45661.kreijack@libero.it> (raw)
In-Reply-To: <1286859944.3013.10.camel@localhost>
On Tuesday, 12 October, 2010, Ian Kent wrote:
> On Mon, 2010-10-11 at 20:08 +0200, Goffredo Baroncelli wrote:
[...]
> > + ret = btrfs_unlink_subvol(trans, root, dir,
> > + dest->root_key.objectid,
> > + dentry->d_name.name,
> > + dentry->d_name.len);
> > + BUG_ON(ret);
>
> Is it really a good idea to add even more dead end BUG_ON() calls
> instead of handling errors when they happen?
>
I agree with your comment, I copied these lines from the ioctl DESTROY_SUBVOL.
Unfortunately I don't have the know-how to handle an error at this level. So I
can only leave the code as the original one.
[...]
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
next prev parent reply other threads:[~2010-10-17 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 18:08 [PATCH V2] Removing a subvolume by an ordinary user Goffredo Baroncelli
2010-10-12 5:05 ` Ian Kent
2010-10-17 15:53 ` Goffredo Baroncelli [this message]
2010-10-18 6:02 ` Ian Kent
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=201010171753.45661.kreijack@libero.it \
--to=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).