Received: by 2002:a05:6520:3645:b029:c0:f950:43e0 with SMTP id l5csp6288613lki; Thu, 4 Mar 2021 09:18:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJyOwfTQhDAdiuZtowtCNeCD+RLaRSP308dEdYTK9zdvvQb5qUk2UcpKdblw+QLOrQi8u1a3 X-Received: by 2002:aa7:d4ca:: with SMTP id t10mr5470436edr.388.1614878316413; Thu, 04 Mar 2021 09:18:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614878316; cv=none; d=google.com; s=arc-20160816; b=VUgejWO7PWWVh40U0sM6NFOWz0pCnYjWYQMR+B5ZSExAOFnT6XZ/IRRPKX5Ejp/a/c Kqg8xnikTqyDHIM9WI//SBRbQ1UyFMZv1x/ABcP44zbxm2OnLuz4QcYDd8QiIPXWwb+D GxZuDAiv/jB7QsweoasL55nDTIHp2uAR1ngnZOeNt2pxgqKnpgT25eHBpeuYEragPEaX rA727JbN339Da1/dQRc+uDsLfHVSdDg8DvKJznrSbAk/nCCi/Nk+xFP1nk6Rb86A2K3e Dk7DVgxHP8jU/5lFESWZHbJXM+dr0UMcDWeADv6Fs4v4UzkFxQvUqI7vC4p42E1NSGYd 28Mw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=IkZSxEKmxDnk7+pb9N2UWbsmQ37Zcfk3ifbixBPeSaE=; b=0oseaJdTrQPlQ9QJXVU7I6K7EB/LT7PlI+0JdQajiYZdaRL0y6u4gv2u19g+hxriWF vW1MLpRxqz80aMRkdSdwwxAc/w/zInH+ISmXw7JR7MX0M0EJ4w3loWhZESsMFUQqA/9D 1RBJZC9oMUQiu1DRWsTXFFrv1wPko+OSv8KhRJeNGhLO6LpPTnkFCB7HvePQLitbYb+n 6h+uLq1w4GJIOltjAv7yB+TRCDKwGkXe50h8z0Dj5jLgpOlJzxZvNXoZ6kdca2ceq+8L yOBIiyvjd01FEgXOhwSBYrTpiJ7jsPXaq1imamhU6K/O0womMGFbncIZb49g+flpOuPp bypg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d14si14276573ejd.560.2021.03.04.09.18.13; Thu, 04 Mar 2021 09:18:36 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231163AbhCDMoD (ORCPT + 99 others); Thu, 4 Mar 2021 07:44:03 -0500 Received: from jabberwock.ucw.cz ([46.255.230.98]:52504 "EHLO jabberwock.ucw.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234328AbhCDMn6 (ORCPT ); Thu, 4 Mar 2021 07:43:58 -0500 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id 2BFAA1C0B87; Thu, 4 Mar 2021 13:43:15 +0100 (CET) Date: Thu, 4 Mar 2021 13:43:14 +0100 From: Pavel Machek To: Linus Torvalds Cc: Linux Kernel Mailing List Subject: Re: A note on the 5.12-rc1 tag Message-ID: <20210304124314.GA9979@duo.ucw.cz> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > Hey peeps - some of you may have already noticed that in my public git > tree, the "v5.12-rc1" tag has magically been renamed to > "v5.12-rc1-dontuse". It's still the same object, it still says > "v5.12-rc1" internally, and it is still is signed by me, but the > user-visible name of the tag has changed. >=20 > The reason is fairly straightforward: this merge window, we had a very > innocuous code cleanup and simplification that raised no red flags at > all, but had a subtle and very nasty bug in it: swap files stopped > working right. And they stopped working in a particularly bad way: > the offset of the start of the swap file was lost. >=20 > Swapping still happened, but it happened to the wrong part of the > filesystem, with the obvious catastrophic end results. Fun :-(. > One additional reason for this note is that I want to not just warn > people to not run this if you have a swapfile - even if you are > personally not impacted (like I am, and probably most people are - > swap partitions all around) - I want to make sure that nobody starts > new topic branches using that 5.12-rc1 tag. I know a few developers > tend to go "Ok, rc1 is out, I got all my development work into this > merge window, I will now fast-forward to rc1 and use that as a base > for the next release". Don't do it this time. It may work perfectly > well for you because you have the common partition setup, but it can > end up being a horrible base for anybody else that might end up > bisecting into that area. Would it make sense to do a -rc2, now, so new topic branches can be started on that one? Best regards, Pavel --=20 http://www.livejournal.com/~pavelmachek --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRPfPO7r0eAhk010v0w5/Bqldv68gUCYEDV4gAKCRAw5/Bqldv6 8nTqAKCDoqcnnX2pETJIK3lSxsFt1rzDRACcCT8RzKKz/hPm21N+/SdbLff1HyY= =yeY7 -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--