Created attachment 1874585 [details]
File: backtrace

Created attachment 1874586 [details]
File: core_backtrace

Created attachment 1874587 [details]
File: cpuinfo

Created attachment 1874588 [details]
File: dso_list

Created attachment 1874589 [details]
File: environ

Created attachment 1874590 [details]
File: exploitable

Created attachment 1874591 [details]
File: limits

Created attachment 1874592 [details]
File: maps

Created attachment 1874593 [details]
File: mountinfo

Created attachment 1874594 [details]
File: open_fds

Created attachment 1874595 [details]
File: proc_pid_status

Created attachment 1874596 [details]
File: var_log_messages

Patch submitted upstream: https://lore.kernel.org/linux-nfs/20220425195948.2627428-1-tbecker@redhat.com/T/#u

Here is a scratch build which has the upstream patch that should fix this problem

https://koji.fedoraproject.org/koji/taskinfo?taskID=86356846

Could you please verify it does fix the problem... tia!

Similar problem has been detected:

I beleive that this was caused by putting my notebook in suspend mode as the timing of going into suspend mode and the
application crash time are about the same. I had active nfs mounts and exports at the time.

reporter:       libreport-2.17.1
backtrace_rating: 4
cgroup:         0::/system.slice/systemd-udevd.service/udev
cmdline:        /usr/libexec/nfsrahead zfs-1
crash_function: dev_from_arg
executable:     /usr/libexec/nfsrahead
journald_cursor: s=c667eb9c60a64df7bcc156da25f2fe86;i=69ac21;b=59d0f944bc4448f6a1d4a7266fea64d2;m=b04ae00;t=5ddbd69b511e8;x=c4f0f5944d2e2aa6
kernel:         5.17.4-300.fc36.x86_64
package:        nfs-utils-1:2.6.1-1.rc4.fc37
reason:         nfsrahead killed by SIGSEGV
rootdir:        /
runlevel:       unknown
type:           CCpp
uid:            0

(In reply to Nathan Mourey II from comment #15)
> Similar problem has been detected:
> 
> I beleive that this was caused by putting my notebook in suspend mode as the
> timing of going into suspend mode and the
> application crash time are about the same. I had active nfs mounts and
> exports at the time.
> 
> reporter:       libreport-2.17.1
> backtrace_rating: 4
> cgroup:         0::/system.slice/systemd-udevd.service/udev
> cmdline:        /usr/libexec/nfsrahead zfs-1
> crash_function: dev_from_arg
> executable:     /usr/libexec/nfsrahead
> journald_cursor:
> s=c667eb9c60a64df7bcc156da25f2fe86;i=69ac21;
> b=59d0f944bc4448f6a1d4a7266fea64d2;m=b04ae00;t=5ddbd69b511e8;
> x=c4f0f5944d2e2aa6
> kernel:         5.17.4-300.fc36.x86_64
> package:        nfs-utils-1:2.6.1-1.rc4.fc37
> reason:         nfsrahead killed by SIGSEGV
> rootdir:        /
> runlevel:       unknown
> type:           CCpp
> uid:            0

Where you using the nfs-utils in the scratch build in Comment 14?

@Steve Dickson
No.

(In reply to Nathan Mourey II from comment #17)
> @Steve Dickson
> No.

Well in bug 2077585, the problem was fix although logging is a bit too verbose... Which will be fixed.

FEDORA-2022-b60800de8a has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b60800de8a

FEDORA-2022-b60800de8a has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b60800de8a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b60800de8a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-b60800de8a has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

The problem appears to have been remediated, else I expect that I would have reported occurrence of it subsequently.