From: Stanislav Brabec <sbrabec@suse.cz>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org, "David Štěrba" <dsterba@suse.cz>
Subject: Re: [PATCH] libmount: handle btrfs default subvolume mount
Date: Thu, 21 Jan 2016 16:24:55 +0100 [thread overview]
Message-ID: <56A0F847.5000000@suse.cz> (raw)
In-Reply-To: <20160121094833.67lg22o4la7j7pto@ws.net.home>
Karel Zak wrote:
> On Wed, Jan 20, 2016 at 10:57:07PM +0100, Stanislav Brabec wrote:
>> +/**
>> + * btrfs_get_default_subvol_id:
>> + * @path: Path to mounted btrfs volume
>
> this comment formatting indicate API docs, for private library functions
> we don't use "/**".
>
Should I export this? I think that no.
Well, looking again into libbtrfs, it is also possible to use
btrfs_list_get_default_subvolume() from libbtrfs, as is nearly exactly
the same. But I am not sure, whether it is good to introduce such a
dependency just for a single small function.
P. S.:
David also wrote btrfs_get_default_subvolume_path(), but then we found,
that there is probably better to use subvolid and path saved in
procinfo:
+ The tab.c patch would be much smaller and straightforward.
- Kernel evaluates it when creating procinfo entries, this would
duplicate it.
x Both subvol and subvolid in procinfo were introduced together in the
mainline kernel, and btrfs_get_default_subvolume_path() needs more
ioctl() calls.
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@suse.com
Lihovarská 1060/12 tel: +49 911 7405384547
190 00 Praha 9 fax: +420 284 084 001
Czech Republic http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76
next prev parent reply other threads:[~2016-01-21 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 20:34 [PATCH] libmount: handle btrfs default subvolume mount Stanislav Brabec
2016-01-20 21:51 ` Stanislav Brabec
2016-01-20 21:57 ` Stanislav Brabec
2016-01-21 9:48 ` Karel Zak
2016-01-21 15:24 ` Stanislav Brabec [this message]
2016-01-21 15:37 ` Karel Zak
2016-01-21 15:45 ` Karel Zak
2016-01-21 17:24 ` Stanislav Brabec
2016-01-22 8:42 ` David Sterba
2016-01-21 21:58 ` Stanislav Brabec
2016-01-26 10:15 ` Karel Zak
2016-01-28 14:22 ` Stanislav Brabec
2016-02-01 12:18 ` Karel Zak
2016-02-01 15:38 ` Stanislav Brabec
2016-02-02 10:11 ` Karel Zak
2016-02-02 15:04 ` Stanislav Brabec
2016-02-02 18:43 ` Karel Zak
2016-02-02 19:36 ` Stanislav Brabec
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=56A0F847.5000000@suse.cz \
--to=sbrabec@suse.cz \
--cc=dsterba@suse.cz \
--cc=kzak@redhat.com \
--cc=util-linux@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