Hello Yair,
> Our kernel is vanilla 5.10.104 with the aufs merged (commit 9e76bce469e6 (I
> guess aufs version 5.10.82)).
> We compile our kernel from source with aufs remote merged. When compiling
> without the commits from this year (i.e. merging 919d03004ab4 from
> 2021-12-27) this doesn't happen (I didn't have time for a full bisect).
>
> The exact command that fails in our case is:
> mount -oremount aufs /var
This bug may be same as the one PB (on github) reported recently.
The fix will be released tomorrow, while I am not sure whether it solves
your case or not. Anyway here I attach it. Apply the patch and test
it.
J. R. Okajima
commit 25f5c5fdcb1b6c2a47f58b59c74547538b7b7c2a
Author: J. R. Okajima <hooanon...@gmail.com>
Date: Mon Mar 7 07:34:13 2022 +0900
aufs: bugfix, umount passes NULL to ->parse_monolithic()
The parameter "void *data" is NULL in unmounting.
Reported-by: PB on github
Signed-off-by: J. R. Okajima <hooanon...@gmail.com>
See-also: https://github.com/sfjro/aufs5-standalone/issues/9
diff --git a/fs/aufs/fsctx.c b/fs/aufs/fsctx.c
index aa9b444438c20..739531e2d2908 100644
--- a/fs/aufs/fsctx.c
+++ b/fs/aufs/fsctx.c
@@ -1091,7 +1091,7 @@ static int au_fsctx_parse_monolithic(struct fs_context *fc, void *data)
str = data;
AuDbg("str %s\n", str);
- while (1) {
+ while (str) {
u = is_colonopt(str);
if (u)
str[u] = '=';
