From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6466EC4361B for ; Mon, 14 Dec 2020 20:37:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1D4DD2246B for ; Mon, 14 Dec 2020 20:37:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2503150AbgLNUhQ (ORCPT ); Mon, 14 Dec 2020 15:37:16 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:35785 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2503212AbgLNUg5 (ORCPT ); Mon, 14 Dec 2020 15:36:57 -0500 Received: from callcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0BEKa8vk008684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 14 Dec 2020 15:36:09 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id 4DB4B420136; Mon, 14 Dec 2020 15:36:08 -0500 (EST) Date: Mon, 14 Dec 2020 15:36:08 -0500 From: "Theodore Y. Ts'o" To: Dmitry Vyukov Cc: Andreas Dilger , LKML , Nathan Chancellor , Nick Desaulniers Subject: Re: UBSAN: shift-out-of-bounds in ext4_fill_super Message-ID: <20201214203608.GJ575698@mit.edu> References: <20201210023638.GP52960@mit.edu> <00000000000024030c05b61412e6@google.com> <20201210182821.GS52960@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (Dropping off-topic lists) On Mon, Dec 14, 2020 at 03:37:37PM +0100, Dmitry Vyukov wrote: > > It's going to make everyone else's tags who pull from ext4.git messy, > > though, with gobs of tags that probably won't be of use to them. It > > does avoid the need to use git fetch --tags --force, and I guess > > people are used to the need to GC tags with the linux-repo. (I had meant to say linux-next repo above.) > syzbot is now prepared and won't fail next time, nor on other similar > trees. Which is good. > So it's really up to you. I'm curious --- are you having to do anything special in terms of deleting old tags to keep the size of the repo under control? Git will keep a tag around indefinitely, so if you have huge numbers of next-YYYYMMDD tags in your repo, the size will grow without bound. Are you doing anything to automatically garbage collect tags to preven this from being a problem? (I am not pulling linux-next every day; only when I need to debug a bug reported against the -next tree, so I just manually delete the tags as necessary. So I'm curious what folks who are following linux-next are doing, and whether they have something specific for linux-next tags, or whether they have a more general solution.) Cheers, - Ted