Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1398573 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2016-05-11 01:30 +0200 |
| Last post | 2016-05-11 01:30 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
linux-next: manual merge of the vfs tree with the overlayfs tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-05-11 01:30 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2016-05-11 01:30 +0200 |
| Subject | linux-next: manual merge of the vfs tree with the overlayfs tree |
| Message-ID | <rxpgd-4fX-1@gated-at.bofh.it> |
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in:
fs/overlayfs/super.c
between commit:
420598d5bf9c ("ovl: ignore permissions on underlying lookup")
from the overlayfs tree and commit:
b9e1d435fdf4 ("ovl_lookup_real(): use lookup_one_len_unlocked()")
from the vfs tree.
I fixed it up (I abitrarily chose the overlayfs version (using
lookup_hash() instead of lookup_one_len_unlocked())) 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
Back to top | Article view | linux.kernel
csiph-web