From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751568AbcGPL0v (ORCPT ); Sat, 16 Jul 2016 07:26:51 -0400 Received: from barbershop.grep.be ([89.106.240.122]:35109 "EHLO barbershop.grep.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751374AbcGPL0s (ORCPT ); Sat, 16 Jul 2016 07:26:48 -0400 Date: Sat, 16 Jul 2016 13:26:32 +0200 From: Wouter Verhelst To: Pranay Srivastava Cc: Alex Bligh , "nbd-general@lists.sourceforge.net" , "linux-kernel@vger.kernel.org" Subject: Re: [Nbd] [PATCH 2/2] nbd: Disallow ioctls on disconnected block device Message-ID: <20160716112632.GA7096@grep.be> References: <1466760574-1916-1-git-send-email-mpa@pengutronix.de> <1466760574-1916-2-git-send-email-mpa@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Speed: Gates' Law: Every 18 months, the speed of software halves. Organization: none User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jul 16, 2016 at 03:38:40PM +0530, Pranay Srivastava wrote: > Okay. So how about we include some negotiated key which goes in with every > request which the server could maintain for clients that can be checked while > resetting the connection with the same server? Wut? > So am I correct that this situation can > indeed happen or the server will throw an error back to client in case > the troubled > nbd-client is trying to reconnect to the original server but requests > are going to > another server? > > If yes to above query then what is the best effort we can do to avoid > such scenarios? Tell userspace not to do stupid things? This isn't a problem. The kernel assumes that whatever userspace does, once the connection is set up again everything's the way it was before. If that's not true, then userspace is to blame, not kernel space. Adding a "key" which we need to pass is going to make things wildly more complicated for no benefit. -- < ron> I mean, the main *practical* problem with C++, is there's like a dozen people in the world who think they really understand all of its rules, and pretty much all of them are just lying to themselves too. -- #debian-devel, OFTC, 2016-02-12