netdev - Re: [patch 4/4] LCS recovery dumps when cable reconnect

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 27 Aug 2008 05:19:32 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Ursula Braun <ursula.braun@...ibm.com>
CC:	netdev@...r.kernel.org, linux-s390@...r.kernel.org,
	"Klaus-D. Wacker" <kdwacker@...ibm.com>
Subject: Re: [patch 4/4] LCS recovery dumps when cable reconnect

Ursula Braun wrote:
> From: Klaus-D. Wacker <kdwacker@...ibm.com>
> 
> LCS recovery dumps in irq routine when CCW address in
> Subchannel Status Word (SCSW) is zero. This occurs
> when recovery is driven after cable reconnect.
> 
> Signed-off-by: Klaus-D. Wacker <kdwacker@...ibm.com>
> Signed-off-by: Ursula Braun <ursula.braun@...ibm.com>
> ---
> 
>  drivers/s390/net/lcs.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff -urpN linux-2.6/drivers/s390/net/lcs.c linux-2.6-patched/drivers/s390/net/lcs.c
> --- linux-2.6/drivers/s390/net/lcs.c	2008-08-20 15:54:46.000000000 +0200
> +++ linux-2.6-patched/drivers/s390/net/lcs.c	2008-08-20 15:55:15.000000000 +0200
> @@ -1412,7 +1412,8 @@ lcs_irq(struct ccw_device *cdev, unsigne
>  	}
>  	/* How far in the ccw chain have we processed? */
>  	if ((channel->state != LCS_CH_STATE_INIT) &&
> -	    (irb->scsw.cmd.fctl & SCSW_FCTL_START_FUNC)) {
> +	    (irb->scsw.cmd.fctl & SCSW_FCTL_START_FUNC) &&
> +	    (irb->scsw.cmd.cpa != 0)) {
>  		index = (struct ccw1 *) __va((addr_t) irb->scsw.cmd.cpa)

applied 1-4


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html