Bug 195145 - net/iet kernel panic on FreeBSD 10.1 release (x64)
Summary: net/iet kernel panic on FreeBSD 10.1 release (x64)
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Xin LI
Depends on:
Reported: 2014-11-18 14:12 UTC by patdung100
Modified: 2016-12-31 17:34 UTC (History)
3 users (show)

See Also:

kgdb where (5.00 KB, text/plain)
2014-11-18 14:12 UTC, patdung100
no flags Details
core.txt.0 (20.34 KB, text/plain)
2014-11-18 14:13 UTC, patdung100
no flags Details
iet port info (891 bytes, text/plain)
2014-11-18 14:13 UTC, patdung100
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description patdung100 2014-11-18 14:12:28 UTC
Created attachment 149555 [details]
kgdb where

1. install iet by:
# pkg install iet

2. setup ietd.conf:
Target iqn.2010-09.org.openindiana:02:gp2esx-clu
        Lun 0 Path=/dev/zvol/storage/gp2esx1,Type=blockio,ScsiId=6589cfc000000003,ScsiSN=ODJLMJNJND
        Lun 1 Path=/dev/zvol/storage/gp2esx2,Type=blockio,ScsiId=6589cfc000000004,ScsiSN=YWM5NJQ5OD

3. start ietd

4. client (vmware esxi 5.1 connect to iscsi target)

5. FreeBSD 10.1 iscsi target server crashed

6. attached is the related crash debug info
Comment 1 patdung100 2014-11-18 14:13:22 UTC
Created attachment 149556 [details]
Comment 2 patdung100 2014-11-18 14:13:40 UTC
Created attachment 149557 [details]
iet port info
Comment 3 Ed Maste freebsd_committer 2014-11-18 15:12:54 UTC
Update product and summary; the panic comes from the port's kernel code.
Comment 4 Edward Tomasz Napierala freebsd_committer 2014-11-20 06:27:48 UTC
I don't know IET that well, it's a third party software ported from Linux, but is there any reason to use it instead of the native target (ctld)?
Comment 5 patdung100 2014-11-20 07:18:34 UTC
Well, I was doing some testing with ietd and compare with cltd.
I thought FreeBSD kernel is stable and should not have crashed easily.
Anyway, if there is no big issue, please consider ticket to have lower priority or closed it later.
Comment 6 Ed Maste freebsd_committer 2014-11-20 13:57:19 UTC
> I thought FreeBSD kernel is stable and should not have crashed easily.

It's not really feasible for us to protect against bugs in kernel code that comes from a 3rd party. The net/iet maintainers or upstream should take a look at this, but presumably over time everyone will transition to the native built-in stack.
Comment 7 patdung100 2014-11-20 16:24:11 UTC
Totally agree.
Comment 8 Mark Linimon freebsd_committer freebsd_triage 2014-11-23 07:36:35 UTC
Over to maintainer.
Comment 9 Rene Ladan freebsd_committer 2016-12-31 17:34:29 UTC
Port expired and removed