On Wed, 2015-01-28 at 23:24 +0200, Sagi Grimberg wrote: > On 1/28/2015 8:24 PM, Chris Moore wrote: > >> On 1/27/2015 6:05 PM, Chris Moore wrote: > >> <SNIP> > >>> I haven't tried testing these against the latest 3.10. I tried > >>> applying them to the RHEL 7.1 Snap3 kernel but they wouldn't apply > >>> cleanly - too many other changes to 3.10 haven't been picked up yet by RH. > >>> > >>> I applied all the changes by hand to RHEL 7.1 and had no problems with > >>> booting, but the first time I try to login from the initiator I get a hang on the > >> target. > >> > >> rrr... > >> > >> > >> Can you share your log (with debug?). This is probably patches 5,6 which > >> might be better heading to 3.12+. > >> > >> Patches 1,2 are harmless obviously. > >> Patches 3,4,8 handle some issues in session teardown sequence. > >> Patches 5,6 handle issues in the login sequence (probably causing your > >> RHEL7.1 to hang...) > >> Patch 7 is a fix for bond failover test case, but won't work without patch 5 > >> applied. > >> > >> Sagi. > > > > I built a 3.10.65 kernel and applied the 8 patches. All 8 applied with no issues. > > The system booted fine and I was able to login from the initiator, no sign of > > the hang I was seeing with RHEL 7.1. > > > > I ran about an hour of I/O to 16 LUNs and did about a dozen cable pulls during > > the I/O run with no issues. > > Hah! good to know... > > > > > So these 8 patches seem to fix the problems I was having before with cable > > pulls causing the target to go out to lunch. Now I need to figure out how > > to get them to work with the RHEL 7.1 kernel. > > > > I think it would be better to apply the deltas between 7.1 and 3.10.65 > and this series on top of it (not sure how easy that would be...). > > I'll try to have a look tomorrow. > > Thanks Chris! Thanks for verifying the series atop 3.10.65 code. If there aren't any objections from Sagi & Co, I'll go ahead and post the series for Greg-KH to pickup for queue-3.10 this afternoon. --nab -- 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
