[Bug 2064843] Re: Brick SEGFAULTs in 11.1

[Bryce Harrington]

Hi Nick,

Sorry for the delay - Athos got tied up with another project, but I can
help in moving this forward.

Thank you for the links to the upstream history, and from that it
appears this is only affecting glusterfs 11.x, thus correctly targets
noble and oracular.

I've reviewed your debdiff and the patch in question.  The changes look
sensible to me, and you've given attention to the patch DEP3 header.
I've tweaked the changelog entry to include a bit more detail, and
retargeted it to oracle.  The changes are on a branch here:

https://code.launchpad.net/~bryce/ubuntu/+source/glusterfs/+git/glusterfs/+ref/ubuntu/oracular-
devel

The fixed package is now uploaded to oracular:

Vcs-Git: https://git.launchpad.net/~bryce/ubuntu/+source/glusterfs
Vcs-Git-Commit: 55391d03e55f519d17f7698e6e6478caf5f53b78
Vcs-Git-Ref: refs/heads/sru-lp2064843-oracular

gpg: ../glusterfs_11.1-4ubuntu1_source.changes: Valid signature from E603B2578FB8F0FB
Checking signature on .dsc
gpg: ../glusterfs_11.1-4ubuntu1.dsc: Valid signature from E603B2578FB8F0FB
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading glusterfs_11.1-4ubuntu1.dsc: done.
  Uploading glusterfs_11.1-4ubuntu1.debian.tar.xz: done.  
  Uploading glusterfs_11.1-4ubuntu1_source.buildinfo: done.  
  Uploading glusterfs_11.1-4ubuntu1_source.changes: done.
Successfully uploaded packages.


** Changed in: glusterfs (Ubuntu Oracular)
       Status: Triaged => Fix Committed

** Changed in: glusterfs (Ubuntu Noble)
       Status: In Progress => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2064843

Title:
  Brick SEGFAULTs in 11.1

Status in glusterfs package in Ubuntu:
  Fix Committed
Status in glusterfs source package in Noble:
  Confirmed
Status in glusterfs source package in Oracular:
  Fix Committed

Bug description:
  [ Impact ]

   * Users experience brick SEGFAULTs under certain not-yet-understood
  scenarios. Some reports include a high percentage of small file I/O. I
  encountered the issue roughly every hour with Minio backed by
  GlusterFS on ZFS.

   * This bug introduces an increased risk of data loss or corruption
  depending on the user's configuration and timing of brick crashes.

   * Core dumps from multiple users revealed that the SEGFAULTs are
  caused by a stack overflow when namespaced inodes are destroyed.

   * The patch removes the recursive call to inode_unref when a
  namespaced inode is destroyed.

  [ Test Plan ]

   * The triggers for the issue are not well understood. I have compiled
  the patch against version 11.1-4build3 of glusterfs and it resolved
  the issue on my system.

  [ Where problems could occur ]

   * It's conceivable that this patch introduces undesired behavior when
  inodes are destroyed, however I highly doubt this scenario as
  __inode_destroy was not recursive before the change which introduced
  the bug.

  [ Other Info ]

   * PR which introduced the bug: https://github.com/gluster/glusterfs/pull/1763
   * PR which added this patch: https://github.com/gluster/glusterfs/pull/4302
   * Issue discussion: https://github.com/gluster/glusterfs/issues/4295

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/2064843/+subscriptions