All of lore.kernel.org
 help / color / mirror / Atom feed
* linux-next: manual merge of the userns tree with the fuse tree
@ 2018-03-21  6:26 Stephen Rothwell
  2018-03-21 14:02 ` Eric W. Biederman
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2018-03-21  6:26 UTC (permalink / raw)
  To: Eric W. Biederman, Miklos Szeredi
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

Hi all,

Today's linux-next merge of the userns tree got a conflict in:

  fs/fuse/dev.c

between commits:

  dbf107b2a7f3 ("fuse: Remove the buggy retranslation of pids in fuse_dev_do_read")
  c9582eb0ff7d ("fuse: Fail all requests with invalid uids or gids")
  8cb08329b080 ("fuse: Support fuse filesystems outside of init_user_ns")

from the fuse tree and commits:

  dbf107b2a7f3 ("fuse: Remove the buggy retranslation of pids in fuse_dev_do_read")
  c9582eb0ff7d ("fuse: Fail all requests with invalid uids or gids")
  8cb08329b080 ("fuse: Support fuse filesystems outside of init_user_ns")

from the userns tree.

These commits seem to have been rebased in the fuse tree on top of

  3b7008b226f3 ("fuse: return -ECONNABORTED on /dev/fuse read after abort")

and modified a bit.

I fixed it up (I used the fuse tree version, but please come to
some arrangement about which is correct) and can carry the fix as
necessary. This is now fixed as far as linux-next is concerned, but any
non trivial conflicts should be mentioned to your upstream maintainer
when your tree is submitted for merging.  You may also want to consider
cooperating with the maintainer of the conflicting tree to minimise any
particularly complex conflicts.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: linux-next: manual merge of the userns tree with the fuse tree
  2018-03-21  6:26 linux-next: manual merge of the userns tree with the fuse tree Stephen Rothwell
@ 2018-03-21 14:02 ` Eric W. Biederman
  0 siblings, 0 replies; 2+ messages in thread
From: Eric W. Biederman @ 2018-03-21 14:02 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Miklos Szeredi, Linux-Next Mailing List, Linux Kernel Mailing List

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi all,
>
> Today's linux-next merge of the userns tree got a conflict in:
>
>   fs/fuse/dev.c
>
> between commits:
>
>   dbf107b2a7f3 ("fuse: Remove the buggy retranslation of pids in fuse_dev_do_read")
>   c9582eb0ff7d ("fuse: Fail all requests with invalid uids or gids")
>   8cb08329b080 ("fuse: Support fuse filesystems outside of init_user_ns")
>
> from the fuse tree and commits:
>
>   dbf107b2a7f3 ("fuse: Remove the buggy retranslation of pids in fuse_dev_do_read")
>   c9582eb0ff7d ("fuse: Fail all requests with invalid uids or gids")
>   8cb08329b080 ("fuse: Support fuse filesystems outside of init_user_ns")
>
> from the userns tree.
>
> These commits seem to have been rebased in the fuse tree on top of
>
>   3b7008b226f3 ("fuse: return -ECONNABORTED on /dev/fuse read after abort")
>
> and modified a bit.
>
> I fixed it up (I used the fuse tree version, but please come to
> some arrangement about which is correct) and can carry the fix as
> necessary. This is now fixed as far as linux-next is concerned, but any
> non trivial conflicts should be mentioned to your upstream maintainer
> when your tree is submitted for merging.  You may also want to consider
> cooperating with the maintainer of the conflicting tree to minimise any
> particularly complex conflicts.

As Miklos has merged these I plan to drop these changes from my tree.

Eric

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-03-21 14:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-21  6:26 linux-next: manual merge of the userns tree with the fuse tree Stephen Rothwell
2018-03-21 14:02 ` Eric W. Biederman

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.