From: Jeff King <peff@peff.net>
To: Xavier Morel <xavier.morel@masklinn.net>
Cc: git@vger.kernel.org
Subject: [PATCH 0/3] actually detect bad file modes in fsck
Date: Wed, 10 Aug 2022 16:59:34 -0400 [thread overview]
Message-ID: <YvQcNpizy9uOZiAz@coredump.intra.peff.net> (raw)
In-Reply-To: <YvQPQUuC+IxO0uo4@coredump.intra.peff.net>
On Wed, Aug 10, 2022 at 04:04:17PM -0400, Jeff King wrote:
> > Maybe downgrade to info or ignore by default then? It might still be
> > an issue for people who wilfully upgraded the diagnostic to error
> > hoping to catch the, but hopefully if they did that they'd rather get
> > the notice later than never?
>
> Yeah, that may be a sensible resolution. All things being equal I think
> "warning" is the right level, but out of caution and the historical
> precedent, maybe downgrading it to "info" is justified.
>
> It should be easy to work that into the patch I showed earlier.
OK, so here are cleaned-up patches to do that.
[1/3]: tree-walk: add a mechanism for getting non-canonicalized modes
[2/3]: fsck: actually detect bad file modes in trees
[3/3]: fsck: downgrade tree badFilemode to "info"
fsck.c | 4 ++--
fsck.h | 2 +-
packfile.c | 2 +-
t/t1450-fsck.sh | 14 ++++++++++++++
t/t5504-fetch-receive-strict.sh | 17 +++++++++++++++++
tree-walk.c | 14 +++++++++-----
tree-walk.h | 8 +++++++-
7 files changed, 51 insertions(+), 10 deletions(-)
-Peff
next prev parent reply other threads:[~2022-08-10 21:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 13:43 fsck: BAD_FILEMODE diagnostic broken / never triggers Xavier Morel
2022-08-09 22:48 ` Jeff King
2022-08-09 23:28 ` Jeff King
2022-08-10 15:01 ` Xavier Morel
2022-08-10 20:04 ` Jeff King
2022-08-10 20:59 ` Jeff King [this message]
2022-08-10 21:01 ` [PATCH 1/3] tree-walk: add a mechanism for getting non-canonicalized modes Jeff King
2022-08-10 21:02 ` [PATCH 2/3] fsck: actually detect bad file modes in trees Jeff King
2022-08-10 21:35 ` Junio C Hamano
2022-08-10 21:46 ` Jeff King
2022-08-10 21:54 ` Junio C Hamano
2022-08-10 21:04 ` [PATCH 3/3] fsck: downgrade tree badFilemode to "info" Jeff King
2022-08-10 22:08 ` Junio C Hamano
2022-08-11 8:33 ` Jeff King
2022-08-11 16:24 ` Junio C Hamano
2022-08-11 9:39 ` [PATCH 0/3] actually detect bad file modes in fsck Ævar Arnfjörð Bjarmason
2022-08-14 7:03 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YvQcNpizy9uOZiAz@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=xavier.morel@masklinn.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).