[Gluster-devel] Meeting minutes for Gluster Community Meeting held on 27th July, 2021
Hi all, # Gluster Community Meeting - 27/07/2021 ### Previous Meeting minutes: - [Meeting Minutes]( https://github.com/gluster/community/tree/master/meetings) ### Date/Time: Check the [community calendar]( https://calendar.google.com/event?action=TEMPLATE&tmeid=MDQ0YmRydTllMXYzdWFoMmpsbjdqNXJlYmNfMjAyMDEwMjdUMDkwMDAwWiBzYWptb2hhbUByZWRoYXQuY29t&tmsrc=sajmoham%40redhat.com&scp=ALL ) ### Bridge - 2nd / 4th Tuesday's, 02:30PM IST - Bridge: https://meet.google.com/cpu-eiue-hvk --- ### Attendance Name (#gluster-dev alias) - company * Ayush Ujjwal - Red Hat * Sunil - Red Hat * Saju Mohammed - Red Hat * Sheetal Pamecha - Red Hat * Ravishankar - Red Hat * Pranith Kumar K - PhonePe * Karthik - Red Hat * Vinayak Hariharmath - Red Hat * Deepshikha - Red Hat * Rakshitha - Red Hat * Chetan More - Red Hat ### User stories * None ### Community * Project metrics: |Metrics| Value | | - | | |[Coverity](https://scan.coverity.com/projects/gluster-glusterfs) | 21 | |[Clang Scan](https://build.gluster.org/job/clang-scan/lastBuild/) | 92 | |[Line coverage]( https://build.gluster.org/job/line-coverage/lastCompletedBuild/Line_20Coverage_20Report/)| 70.8 | |[Function coverage]( https://build.gluster.org/job/line-coverage/lastCompletedBuild/Line_20Coverage_20Report/)| 85.1 | |[Gluster User Queries in last 14 days]( https://lists.gluster.org/pipermail/gluster-users/2021-July/thread.html) | 3 | |[Total Github issues](https://github.com/gluster/glusterfs/issues) | 288 | * Any release updates? * Minor release in August. * Blocker issues across the project? * None * Notable thread from the mailing list * None ### Conferences / Meetups * [SDC India](https://www.snia.org/events/sdcindia) Storage Developer Conference August 5-6, 2021 - Virtual Conference ### GlusterFS - v10 and beyond * Issue will be created to keep the track. ### Developer focus * Any design specs to discuss? * None ### Component status * Arbiter - stable/maintained * AFR - stable/maintained * DHT - stable/maintained * EC - stable/maintained * DOC - stable/maintained * Geo Replication - stable/maintained * Glusterd - stable/maintained * thin-arbiter - stable/maintained ### Recent Blog posts / Document updates * [Open Source Storage]( http://opensource-storage.blogspot.com/2021/07/lets-not-forget-ceph-cli-user.html ) * You can also check out the [repository]( https://github.com/pcuzner/cmon) for better understanding. ### Host * Who will host the next meeting? [Ayush] - Host will need to send out the agenda 24hr - 12hrs in advance to mailing list, and also make sure to send the meeting minutes. - Host will need to reach out to one user at least who can talk about their usecase, their experience, and their needs. - Host needs to send meeting minutes as PR to http://github.com/gluster/community - Host has to send the meeting minutes as a mail to the gluster-devel and gluster-users list. ### Notetaker * Who will take notes from the next meeting? [Ayush] ### RoundTable * Current testing is taking place on CentOS 7. Is it the right time to switch to CentOS 8? ### Action Items on host * Check-in Minutes of meeting for this meeting Regards --- Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] mem-pool.c magic trailer causes SIGBUS, fix or remove?
Hi, The magic trailer added at the end of memory allocations in mem-pool.c doesn't have its alignment ensured. This can lead to SIGBUS and abnormal exits on some platforms (e.g., SPARC64). I have a patch to round-up the header and allocation size to get the right alignment for the trailer (I think). It does complicate the memory allocation a little further. Question is whether it would just be simpler to remove the trailer, and simplify the code? There are a number of external tools that exist to debug memory allocs, from runtime loadable debug malloc libraries, to compiler features (ASAN, etc.), to valgrind. Glusterfs could just rely on those, and so simplify and (perhaps) speed-up its own, general-case memory code. Remove the trailer? Or fix it? regards, -- Paul Jakma | p...@jakma.org | @pjakma | Key ID: 0xD86BF79464A2FF6A Fortune: Many people are secretly interested in life. --- Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
