linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: David Sterba <dsterba@suse.cz>
Cc: lsf-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM ATTEND] Attendance request
Date: Fri, 4 Mar 2016 08:59:06 -0800	[thread overview]
Message-ID: <20160304165906.GB14271@localhost.localdomain> (raw)
In-Reply-To: <20160304165310.GA14271@localhost.localdomain>

On Fri, Mar 04, 2016 at 08:53:15AM -0800, Liu Bo wrote:
> On Fri, Mar 04, 2016 at 03:30:58PM +0100, David Sterba wrote:
> > On Sun, Feb 28, 2016 at 03:16:15PM -0800, Liu Bo wrote:
> > > Hi,
> > > 
> > > I'd like to attend the LSF/MM conference this year.
> > > 
> > > I think I can contribute to a few areas that are being discussed this year:
> > >   - how to provide better information for the filesystem to optimize allocation.
> > >   - power/failure tests
> > >   - performance aspects, etc.
> > > 
> > > Besides that, I'd like to talk about the following,
> > >   - combining overlayfs with btrfs to properly fix overlayfs copy-up slowness.
> > >   - fragmentation control in Copy-On-Write filesystems. (setting a reasonable
> > >     large allocation unit and performing RMW, etc?)
> > >     Since xfs is also going to have reflink, so xfs is also regarded as COW
> > >     FS, having some generic ideas for this topic would help a lot.
> > >   - mount individual subvolumes (in btrfs) with different selinux label, this
> > >     will be useful in container senarios when btrfs being their storage driver.
> > > 
> > > (I've finished the patch for the above selinux label support, but it can ends up
> > > with inode leak if it's not used in the container way, which is assuming the
> > > top subvolume is always being the last one to unmout.)
> > 
> > Do you have the patchset so I can have a look? I've claimed the
> > per-subvolume mount properties in the past and have it almost working.
> > Supporting selinux labels seems to have some overlap, so I'm curious how
> > much code conflicts are there.
> 
> There might be some conflicts since I'm using pseudo superblock for each
> subvolume in that case in order to support selinux label.

I also changed docker's btrfs graphdriver code to mount a
subvolume/snapshot like what devicemapper does so that it can have
different selinux label for each container.

To test it, we have to use "mount -osubvolid=AAA,nosharecache=AAA /disk /mnt"

Thanks,

-liubo

> 
> Here is the patch,
> 
> https://github.com/liubogithub/btrfs-work/commit/00765203698d7e8a795d72488aefc9e19ab70b6e
> 
> Thanks,
> 
> -liubo

  reply	other threads:[~2016-03-04 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28 23:16 [LSF/MM ATTEND] Attendance request Liu Bo
2016-03-04 14:30 ` David Sterba
2016-03-04 16:53   ` Liu Bo
2016-03-04 16:59     ` Liu Bo [this message]
2016-03-04 17:25       ` David Sterba
2016-03-04 18:08         ` Liu Bo
  -- strict thread matches above, loose matches on Subject: below --
2016-02-25 20:23 [LSF/MM ATTEND] attendance request Andreas Dilger

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=20160304165906.GB14271@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linuxfoundation.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).