Andrew Morton wrote: >>> https://bugzilla.kernel.org/show_bug.cgi?id=18252 ... > What you've quoted above appears to be just the aftermath. > https://bugzilla.kernel.org/attachment.cgi?id=29562 indicates that the > kernel earlier crashed in scsi code, perhaps under > scsi_setup_fs_cmnd(). > > The question is: was that actually the first crash, or did an even > earlier one scroll off? It happened overnight. The screenshot https://bugzilla.kernel.org/attachment.cgi?id=29562 shows that there was a lot more logged before it. When I saw it in the morning I assumed that the tail was a repetition of the leading bug trace, but it seems I am mistaken. Florian Mickler wrote: > There was an scsi-related use-after-free OOPS fixed recently and pulled 3 days > ago. > > On Sat, 11 Sep 2010 19:07:44 +0000 > James Bottomley <James.Bottomley@xxxxxxx> wrote: > >> This includes the oops from use after free, a set of qla2xxx fixes, some >> misc warning cleanups from the recently introduced printk issue, an hpsa >> lockup fix and a medium removal bug in sd introduced by the BKL >> pushdown. >> >> The patch is available here: >> >> master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git > > Maybe you are seeing that? > > (reacting to the general-protection-fault preceded by scsi_init in the > attachment jpg) Now that you point it out --- perhaps. Though I haven't looked into the mechanics of the now fixed scsi_ini_io use after free. I am going to update to 2.6.36-rc4 today (I had reverted to 2.6.35 since the report), and if the issue does not return after two weeks or so I will close it as fixed, I suggest. -- Stefan Richter -=====-==-=- =--= -===- http://arcgraph.de/sr/ -- 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
