Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1493929 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2016-09-30 09:50 +0200 |
| Last post | 2016-09-30 12:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
linux-next: manual merge of the akpm-current tree with the userns tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-09-30 09:50 +0200
Re: linux-next: manual merge of the akpm-current tree with the userns tree Ian Kent <raven@themaw.net> - 2016-09-30 12:00 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2016-09-30 09:50 +0200 |
| Subject | linux-next: manual merge of the akpm-current tree with the userns tree |
| Message-ID | <sn0JX-7gi-17@gated-at.bofh.it> |
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
include/linux/mount.h
between commit:
312ddcb332c3 ("mnt: Add a per mount namespace limit on the number of mounts")
from the userns tree and commit:
a0461d15d75c ("vfs: make is_local_mountpoint() usable by others")
from the akpm-current tree.
I fixed it up (see below) 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
diff --cc include/linux/mount.h
index 1172cce949a4,575b7453325a..000000000000
--- a/include/linux/mount.h
+++ b/include/linux/mount.h
@@@ -96,6 -97,12 +97,14 @@@ extern void mark_mounts_for_expiry(stru
extern dev_t name_to_dev_t(const char *name);
+extern unsigned int sysctl_mount_max;
+
+ extern bool __is_local_mountpoint(struct dentry *dentry);
+ static inline bool is_local_mountpoint(struct dentry *dentry)
+ {
+ if (!d_mountpoint(dentry))
+ return false;
+
+ return __is_local_mountpoint(dentry);
+ }
#endif /* _LINUX_MOUNT_H */
[toc] | [next] | [standalone]
| From | Ian Kent <raven@themaw.net> |
|---|---|
| Date | 2016-09-30 12:00 +0200 |
| Subject | Re: linux-next: manual merge of the akpm-current tree with the userns tree |
| Message-ID | <sn2LM-8wm-7@gated-at.bofh.it> |
| In reply to | #1493929 |
On Fri, 2016-09-30 at 17:42 +1000, Stephen Rothwell wrote:
> Hi Andrew,
Hi Stephen,
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> include/linux/mount.h
>
> between commit:
>
> 312ddcb332c3 ("mnt: Add a per mount namespace limit on the number of
> mounts")
>
> from the userns tree and commit:
>
> a0461d15d75c ("vfs: make is_local_mountpoint() usable by others")
>
> from the akpm-current tree.
Yes, this is a problem.
There is a fundamental flaw in the series surrounding commit a0461d15d75c.
In discussion with Eric it was decided a different approach was needed and I'm
holding back on posting an updated series because I was worried something like
this might happen and didn't want to make matters worse.
I definitely don't want this series to go to the Linus tree and it would be
great if you could drop it from the next tree. Eric's patch should then apply
without change.
I had asked Andrew to drop the series but he must have missed my request.
And I thought they had already been dropped but I must have been looking at an
incorrect branch. I'll need to look at the akpm repo. again.
In the meantime all I can offer is the patch names corresponding to the
descriptions.
They are:
fs-make-is_local_mountpoint-usable-by-others.patch
fs-add-have_local_submounts.patch
autofs-make-mountpoint-checks-namespace-aware.patch
fs-remove-unused-have_submounts-function.patch
Sorry for the inconvenience.
Ian
>
> I fixed it up (see below) 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.
>
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web