netdev - Re: via velocity trivial patch

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:	Fri, 8 May 2009 21:29:48 +0200
From:	Francois Romieu <romieu@...zoreil.com>
To:	Radek Podgorny <radek@...gorny.cz>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: via velocity trivial patch

Radek Podgorny <radek@...gorny.cz> :
[...]
> Anyway, I've verified this is really happening on my hardware when
> multiple via velocity devices share the same interrupt. The one the
> interrupt is for reads the correct ISR value, the others sometimes read
> 0 and sometimes 0xffffffff. I'm not educated enough to tell why.

Your quad port network card includes its own pci bus, right ?
If so can you send a 'lspci -vt' of the host ?

> Reasons to include the fix:
> 1) Someone smarter than me suggested it (Jeff Garzik).
> 2) Fixed my problem.
> 3) Does not introduce a new problem.

3. probably stands: there is no reason for the driver to see a
0xffffffff interupt status register (hardware fault or unplug apart).

Well, almost:

$ grep mac.*isr drivers/net/via-velocity.h
#define mac_read_isr(regs)              readl(&((regs)->ISR))
#define mac_write_isr(regs, x)          writel((x),&((regs)->ISR))
#define mac_clear_isr(regs)             writel(0xffffffffL,&((regs)->ISR))

I can figure that there is a window through which the 2nd, 3rd and 4th
devices can read a 0xffffffff when they are brought up but it should
not be noticeable after this stage (and it may happen on the 1st device
as well if it shares its interrupt with some other device).

Does it match your experience ?

> So I'm attaching the patch again. Now with the proper sign-off.

davem's life is probably simpler if you do not include anything
after the patch.

-- 
Ueimor
--
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