From: Sedat Dilek <sedat.dilek@gmail.com>
To: Andrew Watts <akwatts@ymail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [overlayfs/port] overlayfs: v13 port attempt to kernel 3.5
Date: Thu, 16 Aug 2012 23:14:26 +0200 [thread overview]
Message-ID: <CA+icZUX+4mMYqNn5_5EKXTdqbZ25K1HFbsRR5TrToaGJaSPttw@mail.gmail.com> (raw)
In-Reply-To: <20120816204440.GA8808@ymail.com>
On Thu, Aug 16, 2012 at 10:44 PM, Andrew Watts <akwatts@ymail.com> wrote:
> Hi.
>
> I am trying to port the recent work of Andy Whitcroft (for kernel 3.4)
> to kernel 3.5.
>
> Due to changes in *__dentry_open in fs/open.c and to the inode_operations
> struct, overlayfs v13 doesn't apply cleanly.
>
> I am attaching consolidated diffs for both fs/open.c and include/linux/fs.h,
> which contain the substantive changes I made to Andy's work, for review.
>
> Please point out any errors I might have made.
>
> I've not attached the changes I made to the patches against the Locking and
> vfs.txt documentation as those weren't substantive.
>
> Many thanks,
>
Might be easier to collect/extract commits listed in [1]?
If you are on Ubuntu: Check mainline kernels in [2] (quantal) and [3] (precise).
- Sedat -
[1] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-quantal.git&a=search&h=refs/tags/Ubuntu-3.5.0-11.11&st=commit&s=overlayfs
[2] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.2-quantal/
[3] https://launchpad.net/~ubuntu-x-swat/+archive/q-lts-backport/+packages
> ~ Andy
>
next prev parent reply other threads:[~2012-08-16 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 20:44 [overlayfs/port] overlayfs: v13 port attempt to kernel 3.5 Andrew Watts
2012-08-16 21:14 ` Sedat Dilek [this message]
2012-08-17 1:05 ` Andrew Watts
2012-08-17 9:18 ` Sedat Dilek
2012-08-20 10:38 ` J. R. Okajima
2012-08-20 11:26 ` Sedat Dilek
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=CA+icZUX+4mMYqNn5_5EKXTdqbZ25K1HFbsRR5TrToaGJaSPttw@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=akwatts@ymail.com \
--cc=linux-fsdevel@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).