[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160326202618.GA42256@jaegeuk.hsd1.ca.comcast.net>
Date: Sat, 26 Mar 2016 13:26:18 -0700
From: Jaegeuk Kim <jaegeuk@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Eric Biggers <ebiggers3@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux FS Dev Mailing List <linux-fsdevel@...r.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@...ts.sourceforge.net>,
Michael Halcrow <mhalcrow@...gle.com>,
Theodore Ts'o <tytso@....edu>
Subject: Re: [GIT PULL] f2fs updates for v4.6
On Sat, Mar 26, 2016 at 01:04:44PM -0700, Linus Torvalds wrote:
> On Sat, Mar 26, 2016 at 1:00 PM, Jaegeuk Kim <jaegeuk@...nel.org> wrote:
> >
> > After then, as Dave suggested, we needed to move the crypto libraries into
> > common fs/crypto, so that other filesystems can support that in common sense.
> >
> > Please check the below threads about this history.
> > http://www.spinics.net/lists/linux-fsdevel/msg93424.html
>
> That's not the explanation we wanted.
>
> The thing that needs explaining is the "index" change to
> "inode->i_ino", which I undid.
Oh, I made the original uplift patch a year ago and confused with the below
patch at that time.
I missed this, when writing new patches based on the old ones recently.
https://lkml.org/lkml/2015/5/11/1214
I made that patch to resolve the changed page index by fcollapse.
But, simply I noticed that encryption doesn't support fcollapse or finsert.
Thanks,
>
> How/why did that happen?
>
> Linus
Powered by blists - more mailing lists