Project

General

Profile

Actions

Bug #5184

open

Null pointer dereference in zil_replaying during pool export with LU in standby

Added by Dan Vatca about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2014-09-19
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:

Description

While writing on a zvol over comstar I put the LU I am writing to into standby mode using aluaadm, then immediately after I export the pool.
This will trigger a BAD TRAP in zfs due to a null pointer dereference:

ffffff007ca2c830 zil_replaying+0x23(0, ffffff1186993500)
ffffff007ca2c8d0 zvol_log_write+0x62(ffffff11d42b16c0, ffffff1186993500, 32d110000, 1000, 1)
ffffff007ca2c910 zvol_log_write_minor+0x21(ffffff11d42b16c0, ffffff1186993500, 32d110000, 1000, 1)
ffffff007ca2c990 sbd_zvol_copy_write+0x196(ffffff11f20ac498, ffffff007ca2ca40, 1)
ffffff007ca2cad0 sbd_copy_rdwr+0x12e(ffffff1231ad9800, 32d110000, ffffff11d93a2aa8, 2, 1)
ffffff007ca2cb60 sbd_handle_write_xfer_completion+0x245(ffffff1231ad9800, ffffff11df3c7158, ffffff11d93a2aa8, 1)
ffffff007ca2cb80 sbd_dbuf_xfer_done+0x110(ffffff1231ad9800, ffffff11d93a2aa8)
ffffff007ca2cc20 stmf_worker_task+0x3b6(ffffff117d845140)
ffffff007ca2cc30 thread_start+8()

The zil_replaying gets the intent log pointer as NULL , and triggers the panic.

No data to display

Actions

Also available in: Atom PDF