linux-kernel - Re: [PATCH]: PCI Error Recovery: Symbios SCSI device driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Oct 2006 14:24:01 -0500
From:	James Bottomley <James.Bottomley@...elEye.com>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Linas Vepstas <linas@...tin.ibm.com>, linux-scsi@...r.kernel.org,
	linux-pci@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org
Subject: Re: [PATCH]: PCI Error Recovery: Symbios SCSI device driver

On Tue, 2006-10-31 at 11:55 -0700, Matthew Wilcox wrote:
> Is it safe / reasonable / a good idea to sleep for 35 seconds in the EH
> handler?  I'm not that familiar with how the EH code works.  It has its
> own thread, so I suppose that's OK.

Yes, each host has its own thread.  Ordinarily it would be impolite to
delay recovery this long, but I assume that since the card is wedged
there's nothing else it could be doing anyway.

Just for my own edification, what happens on the dual function (dual
channel) boards?  We have two threads there and two separate I/O
processors.  I assume a PCI error will kill both, do we need to do
something about this?

James



> I generally prefer not to be so perlish in conditionals, ie:
> 
>         if ((np->s.device->error_state != pci_channel_io_normal) &&
>             (np->s.device->error_state != 0) {
>                 int timed_out = wait_for_completion_timeout(
>                         &np->s.io_reset_wait, WAIT_FOR_PCI_RECOVERY*HZ);
>                 if (!timed_out)
>                         return SCSI_FAILED;
>         }
> 
> Why is the condition so complicated though?  What does 0 mean if it's
> not io_normal?  At least let's hide that behind a convenience macro:
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/