To be honest, however, I'm not sure if this will pass SRU review. That team tends to want to see a detailed test plan to ensure the issue is definitively found without the patch, and confirmed absent with it. Even if it's just statistically (e.g. "crashes multiple times a day without this fix, but with the fix it should be crash-free for several days) that documents how the upload can be verified.
You may also want to sharpen your pencil on the impact statement. "not yet understood" may be a bit of a red flag that there may be more diagnosis homework needing done.
A stack trace or crash dump would be appropriate to include in the Other Info section. That can often be useful for other users to help them evaluate if they're affected by this same issue or have something unrelated.
For the noble SRU, I've also sponsored the upload of the package for you:
Uploading to ubuntu (via ftp to upload.ubuntu.com): 11.1-4ubuntu0. 1.dsc: done. 11.1-4ubuntu0. 1.debian. tar.xz: done. 11.1-4ubuntu0. 1_source. buildinfo: done. 11.1-4ubuntu0. 1_source. changes: done.
Uploading glusterfs_
Uploading glusterfs_
Uploading glusterfs_
Uploading glusterfs_
Successfully uploaded packages.
To be honest, however, I'm not sure if this will pass SRU review. That team tends to want to see a detailed test plan to ensure the issue is definitively found without the patch, and confirmed absent with it. Even if it's just statistically (e.g. "crashes multiple times a day without this fix, but with the fix it should be crash-free for several days) that documents how the upload can be verified.
You may also want to sharpen your pencil on the impact statement. "not yet understood" may be a bit of a red flag that there may be more diagnosis homework needing done.
A stack trace or crash dump would be appropriate to include in the Other Info section. That can often be useful for other users to help them evaluate if they're affected by this same issue or have something unrelated.
Thanks again for working on this bug!