netdev - Re: [NET-NEXT PATCH 1/3] net: Init NAPI dev_list on napi

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: <20081226.013544.108459397.davem@davemloft.net>
Date:	Fri, 26 Dec 2008 01:35:44 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	jeffrey.t.kirsher@...el.com
Cc:	netdev@...r.kernel.org, jeff@...zik.org,
	peter.p.waskiewicz.jr@...el.com
Subject: Re: [NET-NEXT PATCH 1/3] net: Init NAPI dev_list on napi_del

From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Date: Thu, 25 Dec 2008 01:02:04 -0800

> The recent GRO patches introduced the NAPI removal of devices in
> free_netdev.  For drivers that can change the number of queues during
> driver operation, the NAPI infrastructure doesn't allow the freeing and
> re-addition of NAPI entities without reloading the driver.
> 
> This change reinitializes the dev_list in each NAPI struct on delete,
> instead of just deleting it (and assigning the list pointers to POISON).
> Drivers that wish to remove/re-add NAPI will need to re-initialize the
> netdev napi_list after removing all NAPI instances, before re-adding NAPI
> devices again.
> 
> Signed-off-by: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>

Applied.
--
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