gluster / glusterfs

Gluster Filesystem : Build your distributed storage in minutes
https://www.gluster.org
GNU General Public License v2.0
4.7k stars 1.08k forks source link

[abrt] glusterfs-fuse: gf_io_uring_cq_process_some(): glusterfsd killed by SIGABRT #4104

Open kalebskeithley opened 1 year ago

kalebskeithley commented 1 year ago

Description of problem:

see https://bugzilla.redhat.com/show_bug.cgi?id=2181662

glusterfs-fuse-10.3-1.fc37

Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-2988.slice/user@2988.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-f6b26346-ba1c-429d-afcc-b87ccbb9c93f.scope cmdline: /usr/sbin/glusterfs --process-name fuse --volfile-server=hh5.dmz2.tnss.us --volfile-id=datg /datg crash_function: gf_io_uring_cq_process_some executable: /usr/sbin/glusterfsd journald_cursor: s=8491b0852c31484cbe806239e994eb77;i=f596b;b=29f85d5f0cea4e5cb9b8cb1a024aaa94;m=93a86506;t=5f79d276e2fb5;x=60fbee799b8d00cd kernel: 6.2.7-200.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0

Truncated backtrace: Thread no. 1 (6 frames)

4 gf_io_uring_cq_process_some at gf-io-uring.c:615

5 gf_io_uring_dispatch at gf-io-uring.c:710

6 gf_io_uring_worker at gf-io-uring.c:767

7 gf_io_worker_main at gf-io.c:282

8 gf_io_thread_main at gf-io-common.c:383

10 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

The exact command to reproduce the issue:

The full output of the command that failed:

**Expected results:**
**Mandatory info:** **- The output of the `gluster volume info` command**: **- The output of the `gluster volume status` command**: **- The output of the `gluster volume heal` command**: **- Provide logs present on following locations of client and server nodes - /var/log/glusterfs/ **- Is there any crash ? Provide the backtrace and coredump **Additional info:**
**- The operating system / glusterfs version**: **Note: Please hide any confidential data which you don't want to share in public like IP address, file name, hostname or any other configuration**
xhernandez commented 1 year ago

I found a potential issue in the code and fixed it, but I'm not sure if this completely fixes the issue. Can it be tested again with the provided patch ?