linux-kernel - Re: [1/2] [NET] link_watch: Move link watch list into net

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]

Message-ID: <464398BB.8030606@goop.org>
Date:	Thu, 10 May 2007 15:12:11 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	David Miller <davem@...emloft.net>
CC:	herbert@...dor.apana.org.au, hch@...radead.org, ak@...e.de,
	akpm@...ux-foundation.org, virtualization@...ts.osdl.org,
	linux-kernel@...r.kernel.org, chrisw@...s-sol.org,
	ian.pratt@...source.com, Christian.Limpach@...cam.ac.uk,
	netdev@...r.kernel.org, jeff@...zik.org,
	shemminge@...ux-foundation.org, rusty@...tcorp.com.au,
	Valdis.Kletnieks@...edu
Subject: Re: [1/2] [NET] link_watch: Move link watch list into net_device

David Miller wrote:
> From: Jeremy Fitzhardinge <jeremy@...p.org>
> Date: Thu, 10 May 2007 15:00:05 -0700
>
>   
>> Herbert Xu wrote:
>>     
>>> [NET] link_watch: Move link watch list into net_device
>>>
>>> These days the link watch mechanism is an integral part of the
>>> network subsystem as it manages the carrier status.  So it now
>>> makes sense to allocate some memory for it in net_device rather
>>> than allocating it on demand.
>>>       
>> I think there's a problem with one of these two patches.
>>     
>
> Yes, there are :-)
>
> Did you catch the follow-on bug fixes?
>   

Nope.  Guess I got dropped from the cc: list.  Was this on lkml or netdev?

    J

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