-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.2
-
None
-
None
-
None
-
rhel-storage-management
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
## Crash Analysis### Root Cause
The process terminated due to a **failed assertion** that triggered SIGABRT:```
Assertion Location: udiskslinuxdriveobject.c:196
Assertion Condition: device != NULL
Function: udisks_linux_drive_object_constructor()
```
### Call Stack Analysis**Primary Call Path**:
```
#0 __pthread_kill_implementation() - System call to terminate process
#1 raise() - Send SIGABRT signal
#2 abort() - Program termination
#3 g_assertion_message() - GLib assertion handler
#4 g_assertion_message_expr() - GLib assertion message formatting
#5 udisks_linux_drive_object_constructor() ← **CRASH POINT**
#6 g_object_new_with_custom_constructor() - GObject constructor
#7 g_object_new_valist() - GObject creation
#8 g_object_new() - GObject creation entry point
#9 handle_block_uevent_for_drive() - Handle drive block device UEvent
#10 udisks_linux_provider_handle_uevent() - Linux provider UEvent handler
#11 ensure_modules() - Module loading/management
```
not sure the reproducer, just see it one time and get the udisks2 coredump file,
so use the AI to analysis the coredump file and get helpful info.