http://bugzilla.kernel.org/show_bug.cgi?id=11898 ------- Comment #11 from anonymous@xxxxxxxxxxxxxxxxxxxx 2008-11-04 18:11 ------- Reply-To: James.Bottomley@xxxxxxxxxxxxxxxxxxxxx On Tue, 2008-11-04 at 19:55 -0600, Mike Christie wrote: > bugme-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > http://bugzilla.kernel.org/show_bug.cgi?id=11898 > > > > > > > > > > > > ------- Comment #9 from alex.shi@xxxxxxxxx 2008-11-04 17:32 ------- > > I did bisect for this bug and find the following commit cause this problem. > > > > commit f0c0a376d0fcd4c5579ecf5e95f88387cba85211 > > Author: Mike Christie <michaelc@xxxxxxxxxxx> > > Ok, I am looking into this. I have a theoretical case that might trigger an endless loop: Supposing we actually get a two deep starved list. On first pass, we process the first entry, but set starved_head to be it. On second pass, we get a host_busy. Now we will loop forever (because we have a single entry sdev and it's not starved_head) under the host lock, which means we can never unbusy the host. A fix would be to set starved_head to NULL after we delete sdev from the list. James -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
