From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 193041] New: iSCSI initiator: mkfs.ext4 + mount triggers kernel oops
Date: Sat, 21 Jan 2017 00:06:13 +0000 [thread overview]
Message-ID: <bug-193041-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=193041
Bug ID: 193041
Summary: iSCSI initiator: mkfs.ext4 + mount triggers kernel
oops
Product: IO/Storage
Version: 2.5
Kernel Version: v4.10-rc4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: SCSI
Assignee: linux-scsi@vger.kernel.org
Reporter: bvanassche@acm.org
Regression: No
Created attachment 252661
--> https://bugzilla.kernel.org/attachment.cgi?id=252661&action=edit
netconsole output
The following command sequence worked with previous kernels but triggers a
kernel oops with kernel v4.10-rc4:
./restart-lio-iscsi
iscsiadm -m discovery -t st -p localhost
iscsiadm -m node -p localhost -l
mkfs.ext4 /dev/sda
mount /dev/sda /mnt
gdb translates the crash address into the following:
$ gdb ./drivers/scsi/iscsi_tcp.ko
(gdb) list *(iscsi_sw_tcp_xmit_segment+0x84)
0xf54 is in iscsi_sw_tcp_xmit_segment (drivers/scsi/iscsi_tcp.c:272).
267 struct iscsi_sw_tcp_conn *tcp_sw_conn = tcp_conn->dd_data;
268 struct socket *sk = tcp_sw_conn->sock;
269 unsigned int copied = 0;
270 int r = 0;
271
272 while (!iscsi_tcp_segment_done(tcp_conn, segment, 0, r)) {
273 struct scatterlist *sg;
274 unsigned int offset, copy;
275 int flags = 0;
276
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2017-01-21 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 0:06 bugzilla-daemon [this message]
2017-02-01 0:15 ` [Bug 193041] iSCSI initiator: mkfs.ext4 + mount triggers kernel oops bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-193041-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).