-
Notifications
You must be signed in to change notification settings - Fork 326
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
Linux 4.18/4.20 fix #137
base: master
Are you sure you want to change the base?
Linux 4.18/4.20 fix #137
Conversation
Thanks @barrybingo for this fix. |
I'd love to see this merged! |
exfat_super.c
Outdated
void exfat_time_fat2unix(struct exfat_sb_info *sbi, struct timespec *ts, | ||
DATE_TIME_T *tp) | ||
#endif |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would be:
#if LINUX_VERSION_CODE < KERNEL_VERSION(4,18,01)
#define timespec64 timespec
#endif
a good idea?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
up to the repo owner I guess
Also this change is because of this commit
torvalds/linux@95582b0
Which went into kernel v4.18-rc1 so maybe use KERNEL_VERSION(4,18) as the test
You want me to use your change and resubmit the pr?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fixed exfat-dmks-git on my system today (Aug 24 2018) with the latest LInux Kernel on Arch. Was unable to modprobe exfat without this. So, an anecdotal "it works" from me. Thanks!
Hi, I've faced the same issue today.
|
Let's go with Adrian's patch then. |
|
@dpashev Are those changes needed? |
Is this source alive? We requested those changes for about 2 months ago and is still the old version. |
Source: dorimanx/exfat-nofuse#137 Signed-off-by: Deng Qingfang <[email protected]>
Source: dorimanx/exfat-nofuse#137 Signed-off-by: Deng Qingfang <[email protected]>
Source: dorimanx/exfat-nofuse#137 Signed-off-by: Deng Qingfang <[email protected]>
any chance to get this PR merged? |
In torvalds/linux@e462ec50cb a new set of superblock flags was added to replace the original MS_* ones, and in torvalds/linux@e262e32d6b the MS_* flags are suppressed unless uapi/linux/mount.h is included. As is suggested, we should use the new API now.
exfat_{core,super}.c: fix build on 5.0-rc1, MS_* -> SB_*
@barrybingo thanks so much for your work. If work cannot be moved forward it may be a good thing if you could continue the maintenance in your repository. The last merged PR was "Apr 16, 2018" |
I agree, but more importantly, the Arch package should switch over to this repo. The upstream looks dead. It looks like the author hasn't made any commits in github for several months. Are you willing to have the arch package point here? |
I will change the NixOS repository once we can decide on a new maintainer. I do not want another dead repo in 2 months ;) |
I use Arch and require this package working for the foreseeable future and am willing to maintain it in the sense of patching it to work for future kernels as well as compiling, testing and looking over pull requests. I'll open up issues on my fork and look through the outstanding pull requests and issues on this repo to see which require migrating. I've also requested the Arch AUR use my fork. |
@barrybingo awesome! I will change the upstream source to your repo in the next days and remove the manual patches we apply right now. |
Awesome, thanks for your hard work! Just to clarify, we are talking about |
I can confirm that this is working on debian 4.19.0-2-amd64 |
… type. This is tested and works on 5.6.3 as well as 5.5.17. The _TIME_T seems to have been introduced in 2.6.12 and was removed in 412c53a680a97cb1ae2c0ab60230e193bee86387
thank you for the latest fix! (I'm the one who bothered you in the Arch package). That said, it would seem that Exfat works even without this package on 5.6.3 so I ended up uninstalling it. But Im happy to test this anyway. |
Simple change which seems to work fine for issue #136