April 2025 - Devel - Nfs Ganesha List Archives

[M] Change in ...nfs-ganesha[next]: Add Dbus method for showing uid2grp cache

by Lior Suliman (GerritHub)

Attention is currently required from: Frank Filz. Hello Frank Filz, I'd like you to do a code review. Please visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213491?usp=email to review the following change. Change subject: Add Dbus method for showing uid2grp cache ...................................................................... Add Dbus method for showing uid2grp cache Change-Id: I931277cfbefed314487d855d9e6d8f41ec470abd Signed-off-by: Lior Suliman <liorsu(a)gmail.com> --- M src/FSAL/localfs.c M src/include/idmapper.h M src/support/uid2grp_cache.c 3 files changed, 69 insertions(+), 2 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/91/1213491/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213491?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I931277cfbefed314487d855d9e6d8f41ec470abd Gerrit-Change-Number: 1213491 Gerrit-PatchSet: 1 Gerrit-Owner: Lior Suliman <liorsu(a)google.com> Gerrit-Reviewer: Frank Filz <ffilzlnx(a)mindspring.com> Gerrit-Attention: Frank Filz <ffilzlnx(a)mindspring.com>

1 month, 2 weeks

1
0
0 / 0

[M] Change in ...nfs-ganesha[next]: Split Dbus idmapper show to show users and show groups

by Lior Suliman (GerritHub)

Attention is currently required from: Frank Filz. Hello Frank Filz, I'd like you to do a code review. Please visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213490?usp=email to review the following change. Change subject: Split Dbus idmapper show to show users and show groups ...................................................................... Split Dbus idmapper show to show users and show groups Change-Id: I10a373969d8b30d592d2a5cbbac55b14079e50d7 Signed-off-by: Lior Suliman <liorsu(a)gmail.com> --- M src/FSAL/localfs.c M src/idmapper/idmapper_cache.c M src/include/idmapper.h 3 files changed, 70 insertions(+), 18 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/90/1213490/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213490?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I10a373969d8b30d592d2a5cbbac55b14079e50d7 Gerrit-Change-Number: 1213490 Gerrit-PatchSet: 1 Gerrit-Owner: Lior Suliman <liorsu(a)google.com> Gerrit-Reviewer: Frank Filz <ffilzlnx(a)mindspring.com> Gerrit-Attention: Frank Filz <ffilzlnx(a)mindspring.com>

1 month, 2 weeks

1
0
0 / 0

[XS] Change in ...nfs-ganesha[next]: Coverity fix : Fix memory leak

by Sachin Punadikar (GerritHub)

Sachin Punadikar has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213388?usp=email ) Change subject: Coverity fix : Fix memory leak ...................................................................... Coverity fix : Fix memory leak Fix memory leak reported by coverity ID 542667 https://scan8.scan.coverity.com/#/project-view/59588/10586?selectedIssue=... Change-Id: Iecee8cd2661b0d23ffab4f5cbc74dc0678e5d309 Signed-off-by: Sachin Punadikar <sachin.punadikar(a)ibm.com> --- M src/Protocols/NFS/nfs4_op_xattr.c 1 file changed, 5 insertions(+), 4 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/88/1213388/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213388?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: Iecee8cd2661b0d23ffab4f5cbc74dc0678e5d309 Gerrit-Change-Number: 1213388 Gerrit-PatchSet: 1 Gerrit-Owner: Sachin Punadikar <sachin.punadikar(a)ibm.com>

1 month, 2 weeks

1
0
0 / 0

Unsupported FSALs

by Frank Filz

Community, We have a number of FSALs in Ganesha that have no effective support, I'd like to understand who might still be relying on them and if there is anyone who might step up to support them, or whether we can consider removing some on an expedited timeline (normally we declare a FSAL is deprecated in one release, and then remove it in the next). Note that with the magic of git, deleted FSALs could easily be resurrected (though they might not have been updated to match API changes). The risk of not removing unsupported code is first that folks will use code with little or no support and open github issues that cannot effectively be addressed, and that unsupported code may not be properly updated as API changes are made. The following FSALs are suspect: src/FSAL/FSAL_VFS/xfs - this is marginally supported, but could be replaced with plain FSAL_VFS src/FSAL/FSAL_VFS - there is also a Lustre FSAL that is built from this src/FSAL/FSAL_GLUSTER src/FSAL/FSAL_LIZARDFS src/FSAL/FSAL_PROXY_V3 src/FSAL/FSAL_PROXY_V4 src/FSAL/FSAL_KVSFS src/FSAL/FSAL_SAUNAFS Thank for your thoughts Frank Filz

1 month, 2 weeks

8
16
0 / 0

[S] Change in ...nfs-ganesha[next]: Fixed coverity issue - Dereference after null check

by Name of user not set (GerritHub)

yogendra858(a)yahoo.com has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213361?usp=email ) Change subject: Fixed coverity issue - Dereference after null check ...................................................................... Fixed coverity issue - Dereference after null check (313007, 313011, 313021, 313022, 313024, 358483, 358489) Change-Id: Icb29c49f59b482635cb038fb4701b0b10997b47e Signed-off-by: Yogendra Charya Tangalapally <Yogendra.Tangalapally(a)ibm.com> --- M src/FSAL/FSAL_GPFS/export.c M src/FSAL/FSAL_GPFS/fsal_fileop.c M src/FSAL/FSAL_GPFS/fsal_internal.c 3 files changed, 18 insertions(+), 8 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/61/1213361/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213361?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: Icb29c49f59b482635cb038fb4701b0b10997b47e Gerrit-Change-Number: 1213361 Gerrit-PatchSet: 1 Gerrit-Owner: yogendra858(a)yahoo.com

1 month, 2 weeks

1
0
0 / 0

Re: Unsupported FSALs

by Frank Filz

Thanks and welcome aboard. Frank From: Rafi Kavungal [mailto:rafi.kavungal@iternity.com] Sent: Thursday, April 10, 2025 1:35 AM To: Frank Filz <ffilzlnx(a)mindspring.com>; devel(a)lists.nfs-ganesha.org Cc: support(a)lists.nfs-ganesha.org Subject: [NFS-Ganesha-Devel] Re: Unsupported FSALs Wonderful, I will start looking into the issues. I have already added the meeting invites to my calendar. Though it is bit out of my working hours, I hope to join the call regularly. -Rafi Rafi Kavungal Software Engineer | iTernity <mailto:rafi.kavungal@iternity.com> rafi.kavungal(a)iternity.com <tel:+49%20761%2059034810> +49 761 59034810 <http://Homeoffice+Indien> <https://iternity.com/> Website <https://iternity.com/know-how/newsletter/> Newsletter <https://support.iternity.com/> Support Portal <https://iternity.com/privacy/> See our privacy policy if you want us to delete your personal data. iTernity GmbH. Managing Directors: Armin Weißer, Ralf Steinemann. Registered at the District Court Freiburg: HRB-Nr. 701332. USt.Id DE242664311 From: Frank Filz <ffilzlnx(a)mindspring.com <mailto:ffilzlnx@mindspring.com> > Sent: 09 April 2025 12:03 AM To: Rafi Kavungal <rafi.kavungal(a)iternity.com <mailto:rafi.kavungal@iternity.com> >; devel(a)lists.nfs-ganesha.org <mailto:devel@lists.nfs-ganesha.org> Cc: support(a)lists.nfs-ganesha.org <mailto:support@lists.nfs-ganesha.org> Subject: RE: [NFS-Ganesha-Devel] Unsupported FSALs That is great. I just relabled all the FSAL_GLUSTER github issues that were labeled as UNSUPPORTED FSAL as GLUSTER. If you could start taking a look at them, that would be a big help. We also invite you to join our weekly community call, Tuesday’s 7:00 AM Pacific Time. If you’d like me to add you to the calendar invite, I will do so, but here’s the call details: Ganesha community call Tuesday, April 8 · 7:00 – 8:00am Time zone: America/Los_Angeles Google Meet joining info Video call link: <https://meet.google.com/mkh-ctnj-tqz> https://meet.google.com/mkh-ctnj-tqz Or dial: ‪(US) +1 401-702-0462 PIN: ‪495 972 631# More phone numbers: <https://tel.meet/mkh-ctnj-tqz?pin=2844708468265> https://tel.meet/mkh-ctnj-tqz?pin=2844708468265 Or join via SIP: <sip:2844708468265@gmeet.redhat.com> sip:2844708468265@gmeet.redhat.com Thanks Frank From: Rafi Kavungal [ <mailto:rafi.kavungal@iternity.com> mailto:rafi.kavungal@iternity.com] Sent: Tuesday, April 8, 2025 7:17 AM To: Frank Filz < <mailto:ffilzlnx@mindspring.com> ffilzlnx(a)mindspring.com>; <mailto:devel@lists.nfs-ganesha.org> devel(a)lists.nfs-ganesha.org Cc: <mailto:support@lists.nfs-ganesha.org> support(a)lists.nfs-ganesha.org Subject: RE: [NFS-Ganesha-Devel] Unsupported FSALs Hi Frank, We heavily rely on Gluster FSAL for our archive product. We have two active developers working on the project. While we mostly mastered the gluster project, we are confident that we can support the Gluster FSAL with the help of community. Since NFS-Ganesha is such an important part of our project, we will definitely want to do everything to keep Gluster FSAL moving with Ganesha community. Let us know how we can take it forward. Regards Rafi Rafi Kavungal Software Engineer <mailto:rafi.kavungal@iternity.com> rafi.kavungal(a)iternity.com <tel:+49%20761%2059034810> +49 761 59034810 <http://homeoffice+indien/> <https://iternity.com/de/dmea/articles/iternity-at-dmea-2025/> <https://iternity.com/managed-storage/> iTernity GmbH <https://www.linkedin.com/company/iternity-gmbh> <https://www.xing.com/companies/iternitygmbh> <https://www.youtube.com/user/iTernityCAS> <https://iternity.com/know-how/newsletter/> Newsletter See our <https://iternity.com/privacy/> privacy policy if you want us to delete your personal data. iTernity GmbH. Managing Directors: Armin Weißer, Ralf Steinemann. Registered at the District Court Freiburg: HRB-Nr. 701332. USt.Id DE242664311. [v01.023] From: Frank Filz < <mailto:ffilzlnx@mindspring.com> ffilzlnx(a)mindspring.com> Sent: 01 April 2025 02:29 AM To: <mailto:devel@lists.nfs-ganesha.org> devel(a)lists.nfs-ganesha.org Cc: <mailto:support@lists.nfs-ganesha.org> support(a)lists.nfs-ganesha.org Subject: [NFS-Ganesha-Devel] Unsupported FSALs Community, We have a number of FSALs in Ganesha that have no effective support, I’d like to understand who might still be relying on them and if there is anyone who might step up to support them, or whether we can consider removing some on an expedited timeline (normally we declare a FSAL is deprecated in one release, and then remove it in the next). Note that with the magic of git, deleted FSALs could easily be resurrected (though they might not have been updated to match API changes). The risk of not removing unsupported code is first that folks will use code with little or no support and open github issues that cannot effectively be addressed, and that unsupported code may not be properly updated as API changes are made. The following FSALs are suspect: src/FSAL/FSAL_VFS/xfs – this is marginally supported, but could be replaced with plain FSAL_VFS src/FSAL/FSAL_VFS – there is also a Lustre FSAL that is built from this src/FSAL/FSAL_GLUSTER src/FSAL/FSAL_LIZARDFS src/FSAL/FSAL_PROXY_V3 src/FSAL/FSAL_PROXY_V4 src/FSAL/FSAL_KVSFS src/FSAL/FSAL_SAUNAFS Thank for your thoughts Frank Filz

1 month, 3 weeks

1
0
0 / 0

Re: Unsupported FSALs

by Frank Filz

That is great. I just relabled all the FSAL_GLUSTER github issues that were labeled as UNSUPPORTED FSAL as GLUSTER. If you could start taking a look at them, that would be a big help. We also invite you to join our weekly community call, Tuesday’s 7:00 AM Pacific Time. If you’d like me to add you to the calendar invite, I will do so, but here’s the call details: Ganesha community call Tuesday, April 8 · 7:00 – 8:00am Time zone: America/Los_Angeles Google Meet joining info Video call link: https://meet.google.com/mkh-ctnj-tqz Or dial: ‪(US) +1 401-702-0462 PIN: ‪495 972 631# More phone numbers: https://tel.meet/mkh-ctnj-tqz?pin=2844708468265 Or join via SIP: sip:2844708468265@gmeet.redhat.com Thanks Frank From: Rafi Kavungal [mailto:rafi.kavungal@iternity.com] Sent: Tuesday, April 8, 2025 7:17 AM To: Frank Filz <ffilzlnx(a)mindspring.com>; devel(a)lists.nfs-ganesha.org Cc: support(a)lists.nfs-ganesha.org Subject: RE: [NFS-Ganesha-Devel] Unsupported FSALs Hi Frank, We heavily rely on Gluster FSAL for our archive product. We have two active developers working on the project. While we mostly mastered the gluster project, we are confident that we can support the Gluster FSAL with the help of community. Since NFS-Ganesha is such an important part of our project, we will definitely want to do everything to keep Gluster FSAL moving with Ganesha community. Let us know how we can take it forward. Regards Rafi Rafi Kavungal Software Engineer <mailto:rafi.kavungal@iternity.com> rafi.kavungal(a)iternity.com <tel:+49%20761%2059034810> +49 761 59034810 <http://Homeoffice+Indien> <https://iternity.com/de/dmea/articles/iternity-at-dmea-2025/> <https://iternity.com/managed-storage/> iTernity GmbH <https://www.linkedin.com/company/iternity-gmbh> <https://www.xing.com/companies/iternitygmbh> <https://www.youtube.com/user/iTernityCAS> <https://iternity.com/know-how/newsletter/> Newsletter See our <https://iternity.com/privacy/> privacy policy if you want us to delete your personal data. iTernity GmbH. Managing Directors: Armin Weißer, Ralf Steinemann. Registered at the District Court Freiburg: HRB-Nr. 701332. USt.Id DE242664311. [v01.023] From: Frank Filz <ffilzlnx(a)mindspring.com <mailto:ffilzlnx@mindspring.com> > Sent: 01 April 2025 02:29 AM To: devel(a)lists.nfs-ganesha.org <mailto:devel@lists.nfs-ganesha.org> Cc: support(a)lists.nfs-ganesha.org <mailto:support@lists.nfs-ganesha.org> Subject: [NFS-Ganesha-Devel] Unsupported FSALs Community, We have a number of FSALs in Ganesha that have no effective support, I’d like to understand who might still be relying on them and if there is anyone who might step up to support them, or whether we can consider removing some on an expedited timeline (normally we declare a FSAL is deprecated in one release, and then remove it in the next). Note that with the magic of git, deleted FSALs could easily be resurrected (though they might not have been updated to match API changes). The risk of not removing unsupported code is first that folks will use code with little or no support and open github issues that cannot effectively be addressed, and that unsupported code may not be properly updated as API changes are made. The following FSALs are suspect: src/FSAL/FSAL_VFS/xfs – this is marginally supported, but could be replaced with plain FSAL_VFS src/FSAL/FSAL_VFS – there is also a Lustre FSAL that is built from this src/FSAL/FSAL_GLUSTER src/FSAL/FSAL_LIZARDFS src/FSAL/FSAL_PROXY_V3 src/FSAL/FSAL_PROXY_V4 src/FSAL/FSAL_KVSFS src/FSAL/FSAL_SAUNAFS Thank for your thoughts Frank Filz

1 month, 3 weeks

2
1
0 / 0

Consideration for backport to V6.6

by Frank Filz

We have had a bunch of fixes since V6.5 so it's time to start considering backports. Please see this document listing all the patches merged since V6.5: https://docs.google.com/document/d/1OyQxDtfh7SVAqjm2n-XzmpOindAmAMXeAJdfl9q0 9lE/edit?usp=sharing Feel free to discuss here, or comment directly on the document (if you haven't been enabled for comments, just request access and I'll grant it. Thanks Frank Filz

1 month, 3 weeks

1
0
0 / 0

[M] Change in ...nfs-ganesha[next]: NLM: use hashtable_getlatch in state_add_grant_cookie

by Frank Filz (GerritHub)

Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213058?usp=email ) Change subject: NLM: use hashtable_getlatch in state_add_grant_cookie ...................................................................... NLM: use hashtable_getlatch in state_add_grant_cookie This allows holding the latch while the cookie is established, and the lock is taken in the back end if necessary. This should prevent a race condition. Change-Id: Icc4733208e1823bf77f89e0804c605b623151274 Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com> --- M src/SAL/state_lock.c 1 file changed, 46 insertions(+), 32 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/58/1213058/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1213058?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: Icc4733208e1823bf77f89e0804c605b623151274 Gerrit-Change-Number: 1213058 Gerrit-PatchSet: 1 Gerrit-Owner: Frank Filz <ffilzlnx(a)mindspring.com>

1 month, 3 weeks

1
0
0 / 0

Development Community Call

by Frank Filz

These calls happen (almost) every Tuesday 7:00 AM Pacific Time on Google Meet. Here’s the info: Ganesha community call Tuesday, April 8 · 7:00 – 8:00am Time zone: America/Los_Angeles Google Meet joining info Video call link: https://meet.google.com/mkh-ctnj-tqz Or dial: ‪(US) +1 401-702-0462 PIN: ‪495 972 631# More phone numbers: https://tel.meet/mkh-ctnj-tqz?pin=2844708468265 Or join via SIP: sip:2844708468265@gmeet.redhat.com I’m also happy to add you to the invite. And for those still on the invite but are no longer involved with Ganesha and would like to stop getting calendar invites, please send me e-mail and I will remove you. Thanks Frank From: Ruben Alcolea [mailto:ruben.crash@gmail.com] Sent: Saturday, April 5, 2025 3:18 AM To: Frank Filz <ffilzlnx(a)mindspring.com> Cc: devel(a)lists.nfs-ganesha.org; support(a)lists.nfs-ganesha.org Subject: [NFS-Ganesha-Support] Re: [NFS-Ganesha-Devel] Unsupported FSALs I agree with you Frank, How often are the community calls happening? We would like to join you and start participating in them. Can you share the link or the invitation for this meeting? All the best, Rubén El vie, 4 abr 2025 a las 19:54, Frank Filz (<ffilzlnx(a)mindspring.com <mailto:ffilzlnx@mindspring.com> >) escribió: Thanks for that. One thing that would help is more visibility. Is it possible to make the community calls? Tuesday’s 7:00 AM Pacific Time. Thanks Frank From: Ruben Alcolea [mailto:ruben.crash@gmail.com <mailto:ruben.crash@gmail.com> ] Sent: Friday, April 4, 2025 9:54 AM To: Frank Filz <ffilzlnx(a)mindspring.com <mailto:ffilzlnx@mindspring.com> > Cc: devel(a)lists.nfs-ganesha.org <mailto:devel@lists.nfs-ganesha.org> ; support(a)lists.nfs-ganesha.org <mailto:support@lists.nfs-ganesha.org> Subject: [NFS-Ganesha-Support] Re: [NFS-Ganesha-Devel] Unsupported FSALs Hi Frank, I’m writing as a member of the SaunaFS <https://github.com/leil-io/saunafs> community to confirm that we rely on the SaunaFS FSAL for our filesystem. However, we have encountered issues preventing us from migrating to the latest stable v6.5, as our test suite for Ganesha currently passes only for v4.4 but not for v6.5 (21 / 23 pass successfully, 2 tests fail). In the coming days, I plan to update our GitHub Actions pipeline to run our test suite for Ganesha v6.5, making the results available to the Ganesha community. As part of the SaunaFS community, we are committed to support SaunaFS FSAL and keep it up to date with the latest API changes. From our team, we would like to contribute to ensure FSAL_SAUNAFS remains supported and compatible with the latest Ganesha versions. Best regards, Rubén El lun, 31 mar 2025 a las 23:04, Frank Filz (<ffilzlnx(a)mindspring.com <mailto:ffilzlnx@mindspring.com> >) escribió: Community, We have a number of FSALs in Ganesha that have no effective support, I’d like to understand who might still be relying on them and if there is anyone who might step up to support them, or whether we can consider removing some on an expedited timeline (normally we declare a FSAL is deprecated in one release, and then remove it in the next). Note that with the magic of git, deleted FSALs could easily be resurrected (though they might not have been updated to match API changes). The risk of not removing unsupported code is first that folks will use code with little or no support and open github issues that cannot effectively be addressed, and that unsupported code may not be properly updated as API changes are made. The following FSALs are suspect: src/FSAL/FSAL_VFS/xfs – this is marginally supported, but could be replaced with plain FSAL_VFS src/FSAL/FSAL_VFS – there is also a Lustre FSAL that is built from this src/FSAL/FSAL_GLUSTER src/FSAL/FSAL_LIZARDFS src/FSAL/FSAL_PROXY_V3 src/FSAL/FSAL_PROXY_V4 src/FSAL/FSAL_KVSFS src/FSAL/FSAL_SAUNAFS Thank for your thoughts Frank Filz _______________________________________________ Devel mailing list -- devel(a)lists.nfs-ganesha.org <mailto:devel@lists.nfs-ganesha.org> To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org <mailto:devel-leave@lists.nfs-ganesha.org>

1 month, 3 weeks

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

Devel April 2025