[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190725233112.GI1131@ZenIV.linux.org.uk>
Date: Fri, 26 Jul 2019 00:31:12 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Nikolay Borisov <nborisov@...e.com>
Subject: Re: linux-next: run time BUG after merge of the vfs-fixes tree?
On Thu, Jul 25, 2019 at 02:47:12PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> During my qemu boot tests (powerpc64 pseries_le_defconfig) today, I got
> the following BUG:
... caused by mismerge. #fixes does
@@ -1471,10 +1470,11 @@ static void umount_tree(struct mount *mnt, enum umount_tree_flags how)
list_add_tail(&p->mnt_child, &p->mnt_parent->mnt_mounts);
} else {
umount_mnt(p);
- hlist_add_head(&p->mnt_umount, &unmounted);
}
}
change_mnt_propagation(p, MS_PRIVATE);
+ if (disconnect)
+ hlist_add_head(&p->mnt_umount, &unmounted);
}
}
and your merge has dropped the removal part - it has
list_add_tail(&p->mnt_child, &p->mnt_parent->mnt_mounts);
} else {
umount_mnt(p);
hlist_add_head(&p->mnt_umount, &unmounted);
}
}
change_mnt_propagation(p, MS_PRIVATE);
if (disconnect)
hlist_add_head(&p->mnt_umount, &unmounted);
}
}
Should've #work.dcache from there once (equal) #work.dcache2 got pulled ;-/
Powered by blists - more mailing lists