linux-kernel - Re: Spinlock debugging

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:	Mon, 11 Sep 2006 18:24:52 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Andrew Bird <ajb@...eresystems.co.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Spinlock debugging

Ar Llu, 2006-09-11 am 17:38 +0100, ysgrifennodd Andrew Bird:
> Alan
> 	Yes, I have low_latency set for kernels lower than 2.6.17. I'm currently 
> testing using 2.6.15. When you mention 'write method for flow control' do you 
> mean for software XON/XOFF etc?

Yes

Basically in low_latency the following is valid


	driver receives bytes
		flush_to_ldisc
			ldisc calls driver write methods


That means if you have a shared lock for read/write you want to drop it
after you've bashed the hardware and before you flush_to_ldisc. Remember
the IRQ handler is not re-entrant so another IRQ of the same number
won't cause further I/O and out of order receives.

Alan

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