Re: LIO in 4.2.[12] broken?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear Leeman,

CC'ing the target-devel because this is where the issue was discussed.

On Thu, 1 Oct 2015 22:10:10 -0400, Leeman Strout wrote :
> I recently upgraded my kernel to 4.2.1, then due to issues with iSCSI 
> jumped to 4.2.2 in case that fixed things.  Well it didn't so I'm
> back to 4.1.6.
> 
> I am running the _fb series of tools/API and was hoping to hear from 
> anyone on the list that has tried the 4.2 kernel series and might
> have any insight.
> 
> 
> These are the errors I got when trying to connect via the Windows 8 
> iSCSI initiator:
> 
> Got unknown iSCSI OpCode: 0x43
> Cannot recover from unknown opcode while ERL=0, closing iSCSI
> connection.

The issue was reported by Dragan Milivojevic [1] and fixed by the
target maintainer Nicholas A. Bellinger [2]. Linux 4.2.x is impacted
but not prior versions (or Linux 4.3-rc3).

With best regards,

[1] http://www.spinics.net/lists/target-devel/msg10581.html
[2] http://git.kernel.org/cgit/linux/kernel/git/nab/target-pending.git/commit/?id=673681cafa99776e334c3e61cafa2cf115950c32

-- 
Christophe Vu-Brugier
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux