[GIT PULL] orangefs filesystem

[GIT PULL] orangefs filesystem

[Mike Marshall]

The reviews have quieted down, and we hope that orangefs can be
included into 4.3 (or 4.2 even <g>) ...

Please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git orangefs.current

Orangefs touches very little outside of fs/orangefs:

fs/orangefs/downcall.h
fs/orangefs/protocol.h
fs/orangefs/pvfs2-bufmap.h
fs/orangefs/pvfs2-debug.h
fs/orangefs/pvfs2-debugfs.h
fs/orangefs/pvfs2-dev-proto.h
fs/orangefs/pvfs2-kernel.h
fs/orangefs/pvfs2-sysfs.h
fs/orangefs/upcall.h
fs/orangefs/acl.c
fs/orangefs/dcache.c
fs/orangefs/devpvfs2-req.c
fs/orangefs/dir.c
fs/orangefs/file.c
fs/orangefs/inode.c
fs/orangefs/namei.c
fs/orangefs/pvfs2-bufmap.c
fs/orangefs/pvfs2-cache.c
fs/orangefs/pvfs2-debugfs.c
fs/orangefs/pvfs2-mod.c
fs/orangefs/pvfs2-sysfs.c
fs/orangefs/pvfs2-utils.c
fs/orangefs/super.c
fs/orangefs/symlink.c
fs/orangefs/waitqueue.c
fs/orangefs/xattr.c
Documentation/ABI/stable/sysfs-fs-orangefs
Documentation/filesystems/orangefs.txt
fs/Makefile
fs/Kconfig
fs/orangefs/Makefile
fs/orangefs/Kconfig

-Mike Marshall

Re: [GIT PULL] orangefs filesystem

[Andrew Morton]

On Fri, 7 Aug 2015 14:39:08 -0400 Mike Marshall <hubcap@omnibond.com> wrote:

> The reviews have quieted down, and we hope that orangefs can be
> included into 4.3 (or 4.2 even <g>) ...
> 
> Please pull from
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git orangefs.current

The next step is to ask Stephen to add this to linux-next.

Re: [GIT PULL] orangefs filesystem

[Mike Marshall]

Hi Andrew...

Orangefs has been in linux-next for a couple of weeks and has
had numerous improvements because of it...

-Mike

On Fri, Aug 7, 2015 at 4:44 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 7 Aug 2015 14:39:08 -0400 Mike Marshall <hubcap@omnibond.com> wrote:
>
>> The reviews have quieted down, and we hope that orangefs can be
>> included into 4.3 (or 4.2 even <g>) ...
>>
>> Please pull from
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git orangefs.current
>
> The next step is to ask Stephen to add this to linux-next.

Re: [GIT PULL] orangefs filesystem

[Linus Torvalds]

On Sat, Aug 8, 2015 at 2:02 AM, Mike Marshall <hubcap@omnibond.com> wrote:
>> On Fri, Aug 7, 2015 at 4:44 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> The next step is to ask Stephen to add this to linux-next.
>
> Orangefs has been in linux-next for a couple of weeks and has
> had numerous improvements because of it...

Well, then the next step is:

 (a) explain to me why I should pull (which very much involves a
description of what orangefs is and who uses it)

     I use that for the merge message for the commit too, if/once I do
pull, so I want it for posterity as well, but most of all I want it
for actually knowing why, and not feeling like I have to go dig for
such core information.

 (b) doing the pull request during the merge window, because I'm
certainly not pulling a new filesystem into -rc6..

Ok?

                 Linus

Re: [GIT PULL] orangefs filesystem

[Mike Marshall]

Yes, thanks, that clarifies some details for me.

Paying attention to LWN is a good way to become
aware of when the merge window opens, right?

What has seemed counter-intuitive to me, as
the maintainer of an out-of-tree filesystem, is
that I should work to be ready for the merge window, but
since that's when new features show up, that also might be
when I'll find out about changes like dropping .read and
.write from file_operations or changing readdir to iterate...

I have posted orangefs as a patch to fs-devel several
times, and I think the description that I send with the
patch is what you need to see in my next pull
request (during the merge window <g>)...

Thanks again...

-Mike



On Fri, Aug 7, 2015 at 9:24 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Sat, Aug 8, 2015 at 2:02 AM, Mike Marshall <hubcap@omnibond.com> wrote:
>>> On Fri, Aug 7, 2015 at 4:44 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
>>>
>>> The next step is to ask Stephen to add this to linux-next.
>>
>> Orangefs has been in linux-next for a couple of weeks and has
>> had numerous improvements because of it...
>
> Well, then the next step is:
>
>  (a) explain to me why I should pull (which very much involves a
> description of what orangefs is and who uses it)
>
>      I use that for the merge message for the commit too, if/once I do
> pull, so I want it for posterity as well, but most of all I want it
> for actually knowing why, and not feeling like I have to go dig for
> such core information.
>
>  (b) doing the pull request during the merge window, because I'm
> certainly not pulling a new filesystem into -rc6..
>
> Ok?
>
>                  Linus

Re: [GIT PULL] orangefs filesystem

[Jonathan Corbet]

On Sat, 8 Aug 2015 11:26:52 -0400
Mike Marshall <hubcap@omnibond.com> wrote:

> Paying attention to LWN is a good way to become
> aware of when the merge window opens, right?

We'll let you know :)  But the real key is to watch for the 4.2 release,
which is likely to happen on the 16th or the 23rd.

> What has seemed counter-intuitive to me, as
> the maintainer of an out-of-tree filesystem, is
> that I should work to be ready for the merge window, but
> since that's when new features show up, that also might be
> when I'll find out about changes like dropping .read and
> .write from file_operations or changing readdir to iterate...

That's what linux-next is for.  If your filesystem is working there,
there should not be any surprises for you during the merge window.

jon