Hey all,
I see that exfat has landed in Linus' tree for 5.7 and is no longer in staging. Could backporting exfat from there into Fedora's 5.6 kernel tree be done so that we have exfat support in Fedora 32 at GA?
Best regards, Neal
I see that exfat has landed in Linus' tree for 5.7 and is no longer in staging. Could backporting exfat from there into Fedora's 5.6 kernel tree be done so that we have exfat support in Fedora 32 at GA?
It landed upstream Friday and won't land into a Fedora kernel build until Monday, and hence not a rawhide compose until Tuesday and he which is the same day as we freeze F-32 so I personally don't think it's worth the risk. Sure it's new functionality but I personally think we're better off letting it bake in rawhide for a bit and let it land into F-32 once it's rebased to 5.7 and it's had some time to prove out a bit.
Far more interested to make sure the AX200 wifi fixes land. I have two FC32 machines that suffer.
On Mon, 6 Apr 2020 at 00:51, Peter Robinson pbrobinson@gmail.com wrote:
I see that exfat has landed in Linus' tree for 5.7 and is no longer in staging. Could backporting exfat from there into Fedora's 5.6 kernel tree be done so that we have exfat support in Fedora 32 at GA?
It landed upstream Friday and won't land into a Fedora kernel build until Monday, and hence not a rawhide compose until Tuesday and he which is the same day as we freeze F-32 so I personally don't think it's worth the risk. Sure it's new functionality but I personally think we're better off letting it bake in rawhide for a bit and let it land into F-32 once it's rebased to 5.7 and it's had some time to prove out a bit. _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
On Sun, Apr 5, 2020 at 6:00 PM Joel Wirāmu Pauling jwp@redhat.com wrote:
Far more interested to make sure the AX200 wifi fixes land. I have two FC32 machines that suffer.
That should probably be fixed with the 5.6.2 kernel landing, right? As far as I know, that's already fixed in the 5.6 tree. The availability of exfat in Fedora 32 GA would open quite a few doors for cameras and other equipment where media cards using exfat are quite common.
On Sun, 2020-04-05 at 19:29 -0400, Neal Gompa wrote:
On Sun, Apr 5, 2020 at 6:00 PM Joel Wirāmu Pauling jwp@redhat.com wrote:
Far more interested to make sure the AX200 wifi fixes land. I have two FC32 machines that suffer.
That should probably be fixed with the 5.6.2 kernel landing, right? As far as I know, that's already fixed in the 5.6 tree. The availability of exfat in Fedora 32 GA would open quite a few doors for cameras and other equipment where media cards using exfat are quite common.
Well, support will arrive in updates with the 5.7 rebase. It would be nice to have, but the freeze is tomorrow, we try to keep feature backports to a minimum, and no one has actually done the work yet.
All that to say I'm not sure this is the best way to invest our time.
- Jeremy
On Mon, Apr 6, 2020 at 9:46 AM Jeremy Cline jeremy@jcline.org wrote:
On Sun, 2020-04-05 at 19:29 -0400, Neal Gompa wrote:
On Sun, Apr 5, 2020 at 6:00 PM Joel Wirāmu Pauling jwp@redhat.com wrote:
Far more interested to make sure the AX200 wifi fixes land. I have two FC32 machines that suffer.
That should probably be fixed with the 5.6.2 kernel landing, right? As far as I know, that's already fixed in the 5.6 tree. The availability of exfat in Fedora 32 GA would open quite a few doors for cameras and other equipment where media cards using exfat are quite common.
Well, support will arrive in updates with the 5.7 rebase. It would be nice to have, but the freeze is tomorrow, we try to keep feature backports to a minimum, and no one has actually done the work yet.
All that to say I'm not sure this is the best way to invest our time.
To add to this, it isn't even something that has been in Rawhide for a few weeks and had any testing. It literally came in over the weekend. The first build with this driver will happen today. I understand that it is an interesting feature from a user perspective, but if anything, we should be conservative with filesystems. Yes, Samsung has been shipping it for quite some time with their phones, but that is not quite the same use cases Fedora will see. I don't feel comfortable trying to rush this for the Fedora 32 release.
Justin
On Sun, Apr 5, 2020 at 6:50 AM Peter Robinson pbrobinson@gmail.com wrote:
I see that exfat has landed in Linus' tree for 5.7 and is no longer in staging. Could backporting exfat from there into Fedora's 5.6 kernel tree be done so that we have exfat support in Fedora 32 at GA?
It landed upstream Friday and won't land into a Fedora kernel build until Monday, and hence not a rawhide compose until Tuesday and he which is the same day as we freeze F-32 so I personally don't think it's worth the risk. Sure it's new functionality but I personally think we're better off letting it bake in rawhide for a bit and let it land into F-32 once it's rebased to 5.7 and it's had some time to prove out a bit.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/driver...
I know that there are some significant mm related changes in the 5.7 cycle, because I saw Andrew Morton's heads up email. It also includes vfs changes. I have no idea to what degree exFAT depends on the things being changed, but it may not be simple to just take 5.7's exfat and move it into 5.6. While exfat is self-contained in that exfat changes don't affect anything else in the kernel; the reverse isn't the case.
Another way to look at it, if something blows up, how are we going to fix it? What if it blows up only on Fedora and not in mainline 5.7 or 5.6?
-- Chris Murphy
kernel@lists.fedoraproject.org