From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964902AbcALQeV (ORCPT ); Tue, 12 Jan 2016 11:34:21 -0500 Received: from youngberry.canonical.com ([91.189.89.112]:47410 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932748AbcALQeT (ORCPT ); Tue, 12 Jan 2016 11:34:19 -0500 From: Jay Vosburgh To: Lubomir Rintel cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" , Veaceslav Falico , Andy Gospodarek Subject: Re: [PATCH 3/3] bonding: make device count build-time configurable In-reply-to: <1452599916-27511-1-git-send-email-lkundrak@v3.sk> References: <1452599916-27511-1-git-send-email-lkundrak@v3.sk> Comments: In-reply-to Lubomir Rintel message dated "Tue, 12 Jan 2016 12:58:36 +0100." X-Mailer: MH-E 8.5+bzr; nmh 1.5; GNU Emacs 25.0.50 Date: Tue, 12 Jan 2016 08:34:12 -0800 Message-ID: <8166.1452616452@famine> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Lubomir Rintel wrote: >The devices can be created at run-time for quite some time already and the >load-time device creation collides with attempts to create the device of >the same name: > > # rmmod bonding > # ip link add bond0 type bond > RTNETLINK answers: File exists > >This is pretty much the same situation as was with the block loop devices >which was solved by adding a build-time configuration that the >distributions could use as they deem fit while keeping the default for >compatibility. I agree this is annoying, but I would expect distros to leave this set to 1 (for backwards compatibility with scripts that "modprobe bonding" then assume bond0 exists). This leaves the problem in place for the vast majority of users. Is there a reasonable way to resolve this that would actually fix things for regular distro kernel users? -J --- -Jay Vosburgh, jay.vosburgh@canonical.com