netdev - Re: [NET-NEXT PATCH 08/14] e1000e: link up/down messages must follow a specific format

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Nov 2008 11:23:42 -0800
From:	"Jeff Kirsher" <jeffrey.t.kirsher@...el.com>
To:	"Dan Williams" <dcbw@...hat.com>
Cc:	davem@...emloft.net, netdev@...r.kernel.org, jeff@...zik.org,
	"Bruce Allan" <bruce.w.allan@...el.com>
Subject: Re: [NET-NEXT PATCH 08/14] e1000e: link up/down messages must follow a specific format

On Fri, Nov 21, 2008 at 11:04 AM, Dan Williams <dcbw@...hat.com> wrote:
> On Fri, 2008-11-21 at 11:01 -0800, Jeff Kirsher wrote:
>> From: Bruce Allan <bruce.w.allan@...el.com>
>>
>> The system log messages created on a link status change need to follow a
>> specific format to work with tools some customers use.
>
> Um, shouldn't those tools be listening to netlink for carrier events, or
> are these tools run on a separate machine using on some later date using
> the logs from the machine with the e1000e?
>
> Dan
>

>From my understanding these tools are looking at the logs and that is
why we need to have a consistent log message.

-- 
Cheers,
Jeff
--
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