netdev - Re: [PATCH net-next v2 0/5] bonding: patchset for rcu use in bonding

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: <20131027.174458.627996500790326920.davem@davemloft.net>
Date:	Sun, 27 Oct 2013 17:44:58 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	vfalico@...hat.com
Cc:	dingtianhong@...wei.com, fubar@...ibm.com, andy@...yhouse.net,
	nikolay@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/5] bonding: patchset for rcu use in
 bonding

From: Veaceslav Falico <vfalico@...hat.com>
Date: Sun, 27 Oct 2013 22:10:48 +0100

> All the changelogs for the patches are *the same*, and, while they try
> to
> explain what's done overall, the don't explain what's done per-patch,
> why
> it's done and why is it safe to move those locks around.

He did say so, he listed in fact three alternative ways to fix the
locking problem and then explciitly stated which of the three he
choose.

I would have preferred that he did all of this in the initial 0/N
patch posting, but I can't defer forever.
--
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