Received-SPF: pass (google.com: domain of linux-kernel+bounces-118274-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Date: Mon, 25 Mar 2024 18:56:47 -0700
From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <horms@kernel.org>, thomas.perrot@bootlin.com
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>, Claudiu Beznea
 <claudiu.beznea@tuxon.dev>, "David S . Miller" <davem@davemloft.net>, Eric
 Dumazet <edumazet@google.com>, Paolo Abeni <pabeni@redhat.com>,
 netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: macb: allow MTU change when the interface
 is up
Message-ID: <20240325185647.0ad674e9@kernel.org>
In-Reply-To: <20240325205401.GF403975@kernel.org>
References: <20240325152735.1708636-1-thomas.perrot@bootlin.com>
	<20240325205401.GF403975@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 25 Mar 2024 20:54:01 +0000 Simon Horman wrote:
> I'm not sure that it is expected behaviour for an interface
> to reset like this when a change of MTU is requested.
> While conversely I think it is common (if not entirely desirable)
> to prohibit changing the MTU when an interface is up.
> What is the problem being addressed here?

Right..

> >  	dev->mtu = new_mtu;
> >  
> > +	if (reset)
> > +		macb_open(dev);

. imagine admin does this over SSH on a remote box and system 
is under memory pressure. Even ignoring the fact you're not checking
the return value, the result of changing MTU should be either having 
the requested MTU (success) or having the old MTU (failure).
Not "machine drops off the network" :(