From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.tnxip.de (mail.tnxip.de [49.12.77.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9D9402BE651; Wed, 2 Jul 2025 18:59:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=49.12.77.104 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751482788; cv=none; b=qnyJnC3GPFCI3fZ3zPYwhRzGLBMaygt7hEvx3T9ab3hMhash+Ag67/9EFXh1X8JY6E9nK/2cEJTpnITGKU1Fr/ft98Tb/wQ29LLbypj5s8fJSno2Fgg67YwQMfUwU62K5sJyP7Onf8dbf3liRIWYGfE9s9SVN8Rg2pS0nkxSvB4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751482788; c=relaxed/simple; bh=QHrXzmhcjq+tf7zFyEmmqMNmhAWNPWCstCoYDwuWjt4=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=cXQ4nqDK014vOIaA4u9ai0rhoHw+XAyK2Onk1DeVzYujocoU9fwB3OJglVPHJt+nptawRwpWIYSKLr+gmn+LR+EF7nmLFgOx4gxBzqJrfgGvzNa6sGKG4qNC9qSgnR4xQYm1wbeDWi0f9JGhY8X4diIbOOrw/vWJLYx0KP6ow28= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=tnxip.de; spf=pass smtp.mailfrom=tnxip.de; dkim=pass (1024-bit key) header.d=tnxip.de header.i=@tnxip.de header.b=iE/jubqi; dkim=permerror (0-bit key) header.d=tnxip.de header.i=@tnxip.de header.b=fjDuO26c; dkim=pass (1024-bit key) header.d=tnxip.de header.i=@tnxip.de header.b=SW26/YE6; dkim=permerror (0-bit key) header.d=tnxip.de header.i=@tnxip.de header.b=b/DrPuw6; arc=none smtp.client-ip=49.12.77.104 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=tnxip.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=tnxip.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=tnxip.de header.i=@tnxip.de header.b="iE/jubqi"; dkim=permerror (0-bit key) header.d=tnxip.de header.i=@tnxip.de header.b="fjDuO26c"; dkim=pass (1024-bit key) header.d=tnxip.de header.i=@tnxip.de header.b="SW26/YE6"; dkim=permerror (0-bit key) header.d=tnxip.de header.i=@tnxip.de header.b="b/DrPuw6" Received: from gw.tnxip.de (unknown [IPv6:fdc7:1cc3:ec03:1:41c4:f6bf:9765:d776]) by mail.tnxip.de (Postfix) with ESMTPS id D18DD1F508; Wed, 2 Jul 2025 20:49:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tnxip.de; s=mail-vps; t=1751482193; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QHrXzmhcjq+tf7zFyEmmqMNmhAWNPWCstCoYDwuWjt4=; b=iE/jubqic12yzgfhguECgeXwFLfaUdG2lbDggyuFT+JWIUHNFDBlFSVu/9MgMtlVdOLcoz H/coId7izuylyqJ+hqijSp5ID+bPXU+7vwcurTVEsOiqTbiC501yu7CMJBKfpVXLBuYPh7 HxHpmOpr1Z7xUOBZ4aP78nMgzHHHhOk= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tnxip.de; s=mail-vps-ed; t=1751482193; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QHrXzmhcjq+tf7zFyEmmqMNmhAWNPWCstCoYDwuWjt4=; b=fjDuO26crbRSF0bVmRO+lJSefRPFWJRBYPGhr+dDlMSMAnchwjBB8rNZPjfMX733mGTh60 +bY5NGp4tGSfhZCw== Received: from [IPV6:2a04:4540:8c04:1600:d42:34ad:c501:6cc5] (unknown [IPv6:2a04:4540:8c04:1600:d42:34ad:c501:6cc5]) by gw.tnxip.de (Postfix) with ESMTPSA id 8478B3800000000017FE8; Wed, 02 Jul 2025 20:49:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tnxip.de; s=mail-gw; t=1751482193; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QHrXzmhcjq+tf7zFyEmmqMNmhAWNPWCstCoYDwuWjt4=; b=SW26/YE6Nkw2wtr2YrG7+Q3tv/OJT1Wg1NHQYybgyPXTvQr/+iTwJCJm5/QjI+LD25TJn2 kTk6d88O3HIkpMXnUUP1+f1PiPQ2Q/Btf8PaghEhxVeKpevNAirIpx4huYwgtaH9V4NK2F l9xwKzgQPaHi7ZjV8QZ9TUtDr6ZnErA= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tnxip.de; s=mail-gw-ed; t=1751482193; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QHrXzmhcjq+tf7zFyEmmqMNmhAWNPWCstCoYDwuWjt4=; b=b/DrPuw6PzjFdtZoIVuocUtrnF94Giab5lQ0S7r/Lr8J1GpMMxzkHVXIR/QdR13+r5EcWi fDXrA+72zNNjplDw== Message-ID: Date: Wed, 2 Jul 2025 20:49:32 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Betterbird (Linux) Subject: Re: [GIT PULL] bcachefs fixes for 6.16-rc4 To: Kent Overstreet , "Carl E. Thompson" Cc: John Stoffel , Linus Torvalds , linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org References: <26723.62463.967566.748222@quad.stoffel.home> <751434463.112.1751478094192@mail.carlthompson.net> Content-Language: en-US, de-DE From: =?UTF-8?Q?Malte_Schr=C3=B6der?= In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 02.07.25 19:53, Kent Overstreet wrote: > On Wed, Jul 02, 2025 at 10:41:34AM -0700, Carl E. Thompson wrote: >> Kent, at this point in bcachefs' development you want complete control >> over your development processes and timetable that you simply can't >> get in the mainline kernel. It's in your own best interest for you to >> develop out-of-tree for now. > Carl, all I'm doing is stating up front what it's going to take to get > this done right. > > I'm not particularly pushing one way or the other for bcachefs to stay > in; there are pros and cons either way. It'll be disruptive for it to be > out, but if the alternative is disrupting process too much and driving > Linus and I completely completely nuts, that's ok. > > Everyone please be patient. This is a 10+ year process, no one thing is > make or break. > So as a user usually hanging out on IRC and running Kent's trees: I think most of those people actually testing bcachefs are either running bcachefs-master, -rc or some outdated distro kernel. From my perspective I'd think it would be good enough to push for-upstream during the merge window and then only provide further patches if there where regressions or some really bad bug appears that actually eats data (like the one that bit me). If it's "just" stability fixes, well, if people running a distro kernel hit those bugs they'll need to build a -rc kernel anyways to get fixes, those could just build bcachefs-master. When running Linus' tree I am aware and accept that I am not running the absolutely latest code. I've had some pretty bad experience with amdgpu requiring out of tree patches to get my system running free of glitches, which took months to get into upstream. It's annoying, but I accept that. I'd rather have a slightly outdated bcachefs in kernel than not at all. It is good to have a distro kernel I can fall back to if I mess up my own kernel building ;) my 0.02€ /Malte