linux-kernel - Re: [PATCH] e1000e: disable rxhash when try to enable jumbo frame also rxhash and rxcsum have enabled

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: <20120607.181143.231727418873766540.davem@davemloft.net>
Date:	Thu, 07 Jun 2012 18:11:43 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	joe.jin@...cle.com
Cc:	jeffrey.t.kirsher@...el.com, jesse.brandeburg@...el.com,
	bruce.w.allan@...el.com, carolyn.wyborny@...el.com,
	donald.c.skidmore@...el.com, gregory.v.rose@...el.com,
	peter.p.waskiewicz.jr@...el.com, alexander.h.duyck@...el.com,
	john.ronciak@...el.com, guru.anbalagane@...cle.com,
	adnan.misherfi@...cle.com, e1000-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] e1000e: disable rxhash when try to enable jumbo frame
 also rxhash and rxcsum have enabled

From: Joe Jin <joe.jin@...cle.com>
Date: Fri, 08 Jun 2012 09:06:40 +0800

> Upstream commit 70495a5 check if both rxhash and rxcsum enabled when enabling
> jumbo frames and disallowed all of them enabled at the same time.
> 
> Since jumbo frame widely be used in real world, so when try to enable jumbo
> frames but rxhash and rxcsum have enabled, change the default behavior to
> disable receive hashing.
> 
> Signed-off-by: Joe Jin <joe.jin@...cle.com>
> Signed-off-by: Guru Anbalagane <guru.anbalagane@...cle.com>
> Acked-by: Adnan Misherfi <adnan.misherfi@...cle.com>

If I were the Intel developers I would not apply this patch, it sets
a very bad precedence.

The tool tells you that the combination you're attempting to use is
invalid, and the kernel log message tells you exactly why.

The driver should never automatically change configuration settings
not actually requested by the user.
--
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/