linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Oleksandr Natalenko <oleksandr@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Christian Brauner <christian@brauner.io>,
	Stefan Bader <stefan.bader@canonical.com>,
	Kleber Sacilotto de Souza <kleber.souza@canonical.com>,
	Tyler Hicks <tyhicks@canonical.com>,
	Marcelo Henrique Cerri <marcelo.cerri@canonical.com>,
	Brad Figg <brad.figg@canonical.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH 0/1] Small potential fix for shiftfs
Date: Thu, 15 Aug 2019 09:50:45 -0500	[thread overview]
Message-ID: <20190815145045.GY10402@ubuntu-xps13> (raw)
In-Reply-To: <20190815143603.17127-1-oleksandr@redhat.com>

On Thu, Aug 15, 2019 at 04:36:02PM +0200, Oleksandr Natalenko wrote:
> Hey, people.
> 
> I was lurking at shiftfs just out of curiosity and managed to bump into
> a compiler warning that is (as I suppose) easily fixed by the subsequent
> patch.
> 
> Feel free to drag this into your Ubuntu tree if needed. I haven't played
> with it yet, just compiling (because I'm looking for something that is
> bindfs but in-kernel) :).

Thanks for the patch. Christian has actually already sent a patch for
this along with another patch which is still under review:

https://lists.ubuntu.com/archives/kernel-team/2019-July/102449.html

Also note that currently shiftfs is only in Ubuntu distro kernels, and
Ubuntu-specific kernel patches should be directed at
kernel-team@lists.ubuntu.com rather than lkml. If you'll be at LPC,
there's a session to discuss the future of upstreaming shiftfs that you
might find interesting.

Thanks!
Seth

      parent reply	other threads:[~2019-08-15 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 14:36 [PATCH 0/1] Small potential fix for shiftfs Oleksandr Natalenko
2019-08-15 14:36 ` [PATCH 1/1] shiftfs-5.2: use copy_from_user() correctly Oleksandr Natalenko
2019-08-15 14:50 ` Seth Forshee [this message]

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=20190815145045.GY10402@ubuntu-xps13 \
    --to=seth.forshee@canonical.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=brad.figg@canonical.com \
    --cc=christian@brauner.io \
    --cc=kleber.souza@canonical.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.cerri@canonical.com \
    --cc=oleksandr@redhat.com \
    --cc=stefan.bader@canonical.com \
    --cc=tyhicks@canonical.com \
    /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).