netdev - Re: [PATCH] [ETHTOOL]: Add support for large eeproms

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: <20080415.192330.29185957.davem@davemloft.net>
Date:	Tue, 15 Apr 2008 19:23:30 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	thockin@...gle.com
Cc:	msb@...gle.com, netdev@...r.kernel.org, jeff@...zik.org,
	joe@...ches.com, nil@...gle.com, matthew@....cx
Subject: Re: [PATCH] [ETHTOOL]: Add support for large eeproms

From: "Tim Hockin" <thockin@...gle.com>
Date: Tue, 15 Apr 2008 10:07:21 -0700

> On Tue, Apr 15, 2008 at 12:31 AM, David Miller <davem@...emloft.net> wrote:
> >
> >  This looks fine on the surface.
> >
> >  But I wonder what we can do if we have some EEPROM implementation
> >  that can only write the whole time at once, and thus will fail
> >  if you try to do it in pieces?  Do we have such a case?
> >
> >  If so this new code could cause regressions.
> 
> No device that I know of behaves that way.  It's certainly possible,
> but I've never seen any sort of PROM device that has such a
> requirement.

Fair enough, let's apply the patch and see if anything explode :)
--
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