New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kernel 6.7 - aufs-6.6 patch fails #35
Comments
Even after fixing the patch - there is an unrelated? compile error.....
|
PB:
Even after fixing the patch - there is an unrelated? compile error.....
:::
Thanx for the report.
Obviously aufs should follow the changes in mainline kernel.
Hopefully I'll return to aufs in a few months.
In this case, kernel function __mnt_drop_write() seems to be removed.
And I some replacement should be there. Aufs has to find the replacement
and modify to call it.
J. R. Okajima
|
There are a couple of other changes required too, after applying the patches, this is what I've done to get it working with 6.7.y (though I can't say whether this is the "right" way to fix it :) ) |
@tombriden |
Tom Briden:
There are a couple of other changes required too, after applying the patches, this is what I've done to get it working with 6.7.y (though I can't say whether this is the "right" way to fix it :) )
tombriden/linux@14277ff
Thanx for the info.
It must be a good help to every user.
J. R. Okajima
|
Thank you @tombriden |
Later - tried on a laptop with intel graphics and there all was fine - so does look like a Nouveau problem in 6.7 |
I am confirm I am able to boot up Porteus. |
Thanks for the effort, guys. I'm not sure if there's something wrong in the patches provided by @tombriden or if it's just kernel 6.7 being weird, but the memory consumption (after boot) skyrocketed for me: from 900 MB (v6.6.14) to 1.4 GB (v6.7.2). I can easily replicate this issue by just swapping the kernel modules and keeping the whole system intact. So it's definitely something related to the kernel. |
Also, while compiling I noticed this:
|
fulalas:
fs/namespace.c:895:5: error: redefinition of =E2=80=98is_current_mnt_ns=E2=
=80=99
895 | int is_current_mnt_ns(struct vfsmount *mnt)
| ^~~~~~~~~~~~~~~~~
fs/namespace.c:877:5: note: previous definition of =E2=80=98is_current_mn=
t_ns=E2=80=99 with type =E2=80=98int(struct vfsmount *)=E2=80=99
877 | int is_current_mnt_ns(struct vfsmount *mnt)
```
Maybe the mainline kernel added a new function which has a same name of
a function aufs6-base.path adds.
But I couldn't find is_current_mnt_ns() in vanilla v6.7.2.
What is your kernel version?
J. R. Okajima
|
@sfjro, that was my mistake. I got confused with so many patches, hahaha! I'm sorry about that. We hope you'll get back to the project soon. Thanks! |
Aufs simply follows the change in mainline, 3e15dcf 2023-09-11 fs: rename __mnt_{want,drop}_write*() helpers tombriden on github posted his patch containing the same fix before I made this commit. tombriden@14277ff See-also: sfjro/aufs-standalone#35 Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>
Aufs simply follows the change in mainline, 12cd440 2023-10-18 fs: rename inode i_atime and i_mtime fields tombriden on github posted his patch containing the similar (essentially same) fix before I made this commit. tombriden@14277ff See-also: sfjro/aufs-standalone#35 Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>
patch -N -p1 < aufs6-mmap.patch
patching file fs/proc/base.c
Hunk 1 FAILED at 2218.
1 out of 1 hunk FAILED -- saving rejects to file fs/proc/base.c.rej
fails because line 2217 of base.c is now:
Is there an easy fix to try? I guess the 'obvious'??? is:
*path = *file_user_path(vma_pr_or_file(vma));
The text was updated successfully, but these errors were encountered: