From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.223.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 60DC113BC38 for ; Wed, 3 Apr 2024 10:10:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=195.135.223.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712139032; cv=none; b=d0Y+iTbkbtWCXeDkdPACpeL3VNH55k+o6BwNAln0wum67U1HLy3sv8a0e/1mVBCoreO9MFJXiHTAo5iqJtmD9xVFOejbDww5qafhdx6mt/O+haT3WCMrfPfje96rtPScHMretiUj9Q1TowApSyZkEn6g76Z2jigNuTl64NSH0zQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712139032; c=relaxed/simple; bh=KjV4LvoxqIXAbVNeEuiuhGbkTc8ocYSTzJaf+hAyUFI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=nefOiplbUIm85S/oKQS8uNy22xtYgN1gFPSmehGXXGMUhl5zjmFWetmGx8qYpBrRkCmBAxnm7NReiwIE5ue1c31630yGez47ZeRrqFyLERCG2VKc65U4xekBXA1IzT2rvSpewRun3zLKFiGHlxH3Qs6wxJJdZnTxjQi28Uc7BQE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=suse.de; spf=pass smtp.mailfrom=suse.de; dkim=pass (1024-bit key) header.d=suse.de header.i=@suse.de header.b=BR8PMvtF; dkim=permerror (0-bit key) header.d=suse.de header.i=@suse.de header.b=Xqw3Ocnw; arc=none smtp.client-ip=195.135.223.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=suse.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=suse.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=suse.de header.i=@suse.de header.b="BR8PMvtF"; dkim=permerror (0-bit key) header.d=suse.de header.i=@suse.de header.b="Xqw3Ocnw" Received: from imap2.dmz-prg2.suse.org (imap2.dmz-prg2.suse.org [IPv6:2a07:de40:b281:104:10:150:64:98]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id B30E25CB0A; Wed, 3 Apr 2024 10:10:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1712139022; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4Rc/ZgCh87+LiUV/HvO53PyD28E9OrbkTps1z5xQLZw=; b=BR8PMvtFsUluvJ5aRknJXx90W3u/A1ksA+qjrLvgG9ZWmQmmmYIJPqM/YYRjo2QDOGpYB8 U7CfJeAXqUhRJozj2IDVaFr+Bv7qfP4T6LL41+/x0o8kdlORAp0HW3iUXD7XafnpD8phtQ +Ry6FBqXjiUH5FFGP2oIz7taF00IHkM= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1712139022; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4Rc/ZgCh87+LiUV/HvO53PyD28E9OrbkTps1z5xQLZw=; b=Xqw3Ocnw1TXR6ktGvMoRFfg9WWfmb9R2M+gcTDKv4speW7jQX84YrnhdHdzePcvFMvKIW3 4niLAqOUbxXv/fBw== Authentication-Results: smtp-out2.suse.de; dkim=none Received: from imap2.dmz-prg2.suse.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by imap2.dmz-prg2.suse.org (Postfix) with ESMTPS id 9FF771331E; Wed, 3 Apr 2024 10:10:22 +0000 (UTC) Received: from dovecot-director2.suse.de ([2a07:de40:b281:106:10:150:64:167]) by imap2.dmz-prg2.suse.org with ESMTPSA id aWujJQ4rDWaRCAAAn2gu4w (envelope-from ); Wed, 03 Apr 2024 10:10:22 +0000 Date: Wed, 3 Apr 2024 12:10:22 +0200 From: Daniel Wagner To: Keith Busch Cc: Kamaljit Singh , Christoph Hellwig , "linux-nvme@lists.infradead.org" , "linux-block@vger.kernel.org" , "axboe@fb.com" , Gregory Joyce , Nilay Shroff Subject: Re: [Bug Report] nvme-cli commands fails to open head disk node and print error Message-ID: References: Precedence: bulk X-Mailing-List: linux-block@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: B30E25CB0A X-Spamd-Result: default: False [-2.74 / 50.00]; BAYES_HAM(-3.00)[100.00%]; MID_RHS_NOT_FQDN(0.50)[]; NEURAL_HAM_SHORT(-0.13)[-0.637]; MIME_GOOD(-0.10)[text/plain]; MX_GOOD(-0.01)[]; DKIM_SIGNED(0.00)[suse.de:s=susede2_rsa,suse.de:s=susede2_ed25519]; FUZZY_BLOCKED(0.00)[rspamd.com]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_EQ_ADDR_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_TLS_ALL(0.00)[]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_SOME(0.00)[]; DNSWL_BLOCKED(0.00)[2a07:de40:b281:106:10:150:64:167:received,2a07:de40:b281:104:10:150:64:98:from]; RCPT_COUNT_SEVEN(0.00)[8]; R_DKIM_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; SPAMHAUS_XBL(0.00)[2a07:de40:b281:104:10:150:64:98:from] X-Rspamd-Action: no action X-Rspamd-Server: rspamd2.dmz-prg2.suse.org X-Spam-Score: -2.74 X-Spam-Level: X-Spam-Flag: NO On Tue, Apr 02, 2024 at 09:07:55PM -0600, Keith Busch wrote: > On Tue, Apr 02, 2024 at 10:07:25PM +0000, Kamaljit Singh wrote: > > Your question about the nvme-cli version makes me wonder if there is a > > version compatibility matrix (nvme-cli vs kernel) somewhere you could > > point me to? I didn't see such info in the nvme-cli release notes. > > I don't believe there's ever been an intentional incompatibility for > nvme-cli vs. kernel versions. Most of the incompatibility problems come > from sysfs dependencies, but those should not be necessary for the core > passthrough commands on any version pairing. > > And yeah, there should be sane fallbacks for older kernels in case a new > feature introduces a regression, but it's not always perfect. We try to > fix them as we learn about them, so bug reports on the github are useful > for tracking that. Indeed, all new features are auto detected. So if the kernel provides them, nvme-cli/libnvme will be able to use them. Obviously, sometimes there are some regressions but we avoid to increase the minimum kernel dependency. Many things are also behind CONFIG options, thus the only viable way is to auto detect features. Note, these new features are almost all exclusive in the fabric code base. The PCI related bits are pretty stable. > > For example, I've seen issues with newer than nvme-cli v1.16 on Ubuntu > > 22.04 (stock & newer kernels). From a compatibility perspective I do > > wonder whether circumventing a distro's package manager and directly > > installing newer nvme-cli versions might be a bad idea. This could > > possibly become dire if there were intentional version dependencies > > across the stack. > > The struggle is real, isn't it? New protocol features are added upstream > faster than distro package updates provide their users. On the other > hand, distros may be cautious to potential instability. We got a lot of request to provide up to data binaries for old distros. For this reason we have an AppImage binary to play around. So if you want to play with the latest greatest, it's fairly simple to do so.