netdev - Re: [RFC PATCH] Initialize dev_id sysfs attribute to -1 by default

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: <87fvx4mvtl.fsf@nemi.mork.no>
Date:	Thu, 30 May 2013 15:38:46 +0200
From:	Bjørn Mork <bjorn@...k.no>
To:	<Narendra_K@...l.com>
Cc:	<netdev@...r.kernel.org>, <bhutchings@...arflare.com>
Subject: Re: [RFC PATCH] Initialize dev_id sysfs attribute to -1 by default

<Narendra_K@...l.com> writes:

> From: Narendra K <narendra_k@...l.com>
>
> 'dev_id' sysfs attribute is initialized to zero by default.
> It is also zero based. This creates ambiguity in differentiating
> whether the driver set it to zero or it is the default value.
> Initialize 'dev_id' to -1 to make the scenario unambiguous.

I understand your concern, but I don't think you can do this.  It
changes the userspace API, and has some very visible side effects.

Please take a look at net/ipv6/addrconf.c


Bjørn
--
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