netdev - Re: [PATCH net-next v2] rocker: move netevent neigh update to processes context

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]

Date:	Wed, 03 Jun 2015 23:38:29 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sfeldma@...il.com
Cc:	netdev@...r.kernel.org, jiri@...nulli.us,
	simon.horman@...ronome.com, makita.toshiaki@....ntt.co.jp
Subject: Re: [PATCH net-next v2] rocker: move netevent neigh update to
 processes context

From: sfeldma@...il.com
Date: Tue,  2 Jun 2015 20:43:28 -0700

> From: Scott Feldman <sfeldma@...il.com>
> 
> v2:
> 
> Changes based on review:
> 
> - David Miller <davem@...emloft.net> raise problem with system_wq not
>   preserving queue order to execution order.  To fix, use driver-private
>   ordered workqueue to preserve ordering of queued work.
> 
> - Jiri Pirko <jiri@...nulli.us> small change on kfree of work queue item.
> 
> v1:
> 
> In review of Simon's patchset "rocker: transaction fixes". it was noted
> that rocker->neigh_tbl_next_index was unprotected in the call path below
> and could race with other contexts calling rocker_port_ipv4_neigh():

How it rocker->neigh_tbl_next_index not protected?

rocker->neigh_tbl_lock is _always_ held when it is accessed.

This patch, therefore, looks like completely unnecessary complexity
to me.  Furthermore, I would completely prefer if the operation stays
completely synchronous to the call path where the neigh operation
occurs rather than throwing it out to a workqueue.

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