From: Jeff King <peff@peff.net>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, chriscool@tuxfamily.org, gitster@pobox.com,
szeder.dev@gmail.com
Subject: Re: [PATCH v3 4/4] upload-pack.c: introduce 'uploadpackfilter.tree.maxDepth'
Date: Fri, 31 Jul 2020 17:43:11 -0400 [thread overview]
Message-ID: <20200731214311.GB1457058@coredump.intra.peff.net> (raw)
In-Reply-To: <20200731213604.GA1457058@coredump.intra.peff.net>
On Fri, Jul 31, 2020 at 05:36:04PM -0400, Jeff King wrote:
> My suggested patch does introduce more side effects. I think that's OK
> because there really is only a single caller here. But if you wanted it
> cleaner, then I think having allows_filter_choice() fill out an error
> strbuf would eliminate my concern without drastically altering the flow
> of your code.
That could be something like the patch below. banned_filter() could
switch to returning a simple boolean, but I didn't do that here.
I did (as with my other patch) reorder the logic in allows_filter_choice(),
as I think it's much easier to follow by resolving "allowed" to the
fallback earlier. That lets you handle "not allowed at all" first and
early-return (or die) before dealing with type-specific checks.
diff --git a/upload-pack.c b/upload-pack.c
index 131445b212..86786f0e13 100644
--- a/upload-pack.c
+++ b/upload-pack.c
@@ -993,59 +993,60 @@ static int process_deepen_not(const char *line, struct string_list *deepen_not,
}
static int allows_filter_choice(struct upload_pack_data *data,
- struct list_objects_filter_options *opts)
+ struct list_objects_filter_options *opts,
+ struct strbuf *err)
{
const char *key = list_object_filter_config_name(opts->choice);
struct string_list_item *item = string_list_lookup(&data->allowed_filters,
key);
- int allowed = -1;
+ int allowed;
if (item)
allowed = (intptr_t) item->util;
+ else
+ allowed = data->allow_filter_fallback;
- if (allowed != 0 &&
- opts->choice == LOFC_TREE_DEPTH &&
- opts->tree_exclude_depth > data->tree_filter_max_depth)
+ if (!allowed) {
+ strbuf_addf(err, "filter '%s' not supported", key);
return 0;
+ }
+
+ if (opts->choice == LOFC_TREE_DEPTH &&
+ opts->tree_exclude_depth > data->tree_filter_max_depth) {
+ strbuf_addf(err, "tree filter maximum depth is %lu, but got %lu",
+ data->tree_filter_max_depth, opts->tree_exclude_depth);
+ return 0;
+ }
- if (allowed > -1)
- return allowed;
- return data->allow_filter_fallback;
+ return 1;
}
static struct list_objects_filter_options *banned_filter(
struct upload_pack_data *data,
- struct list_objects_filter_options *opts)
+ struct list_objects_filter_options *opts,
+ struct strbuf *err)
{
size_t i;
- if (!allows_filter_choice(data, opts))
+ if (!allows_filter_choice(data, opts, err))
return opts;
if (opts->choice == LOFC_COMBINE)
for (i = 0; i < opts->sub_nr; i++) {
struct list_objects_filter_options *sub = &opts->sub[i];
- if (banned_filter(data, sub))
+ if (banned_filter(data, sub, err))
return sub;
}
return NULL;
}
static void die_if_using_banned_filter(struct upload_pack_data *data)
{
- struct list_objects_filter_options *banned = banned_filter(data,
- &data->filter_options);
struct strbuf buf = STRBUF_INIT;
+ struct list_objects_filter_options *banned =
+ banned_filter(data, &data->filter_options, &buf);
if (!banned)
return;
- strbuf_addf(&buf, "git upload-pack: filter '%s' not supported",
- list_object_filter_config_name(banned->choice));
- if (banned->choice == LOFC_TREE_DEPTH &&
- data->tree_filter_max_depth != ULONG_MAX)
- strbuf_addf(&buf, _(" (maximum depth: %lu, but got: %lu)"),
- data->tree_filter_max_depth,
- banned->tree_exclude_depth);
-
packet_writer_error(&data->writer, "%s\n", buf.buf);
die("%s", buf.buf);
}
next prev parent reply other threads:[~2020-07-31 21:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 1:48 [PATCH v2 0/4] upload-pack: custom allowed object filters Taylor Blau
2020-07-23 1:48 ` [PATCH v2 1/4] list_objects_filter_options: introduce 'list_object_filter_config_name' Taylor Blau
2020-07-23 1:49 ` [PATCH v2 2/4] upload-pack.c: allow banning certain object filter(s) Taylor Blau
2020-07-23 1:49 ` [PATCH v2 3/4] upload-pack.c: pass 'struct list_objects_filter_options *' Taylor Blau
2020-07-23 1:49 ` [PATCH v2 4/4] upload-pack.c: introduce 'uploadpackfilter.tree.maxDepth' Taylor Blau
2020-07-23 20:43 ` [PATCH v2 0/4] upload-pack: custom allowed object filters SZEDER Gábor
2020-07-24 16:51 ` Taylor Blau
2020-07-24 19:51 ` Jeff King
2020-07-27 14:25 ` Taylor Blau
2020-07-27 19:34 ` SZEDER Gábor
2020-07-27 19:36 ` Taylor Blau
2020-07-27 19:42 ` Jeff King
2020-07-27 19:59 ` SZEDER Gábor
2020-07-27 20:03 ` Taylor Blau
2020-07-31 20:26 ` [PATCH v3 " Taylor Blau
2020-07-31 20:26 ` [PATCH v3 1/4] list_objects_filter_options: introduce 'list_object_filter_config_name' Taylor Blau
2020-07-31 20:26 ` [PATCH v3 2/4] upload-pack.c: allow banning certain object filter(s) Taylor Blau
2020-07-31 20:54 ` Jeff King
2020-07-31 21:20 ` Taylor Blau
2020-07-31 20:26 ` [PATCH v3 3/4] upload-pack.c: pass 'struct list_objects_filter_options *' Taylor Blau
2020-07-31 20:26 ` [PATCH v3 4/4] upload-pack.c: introduce 'uploadpackfilter.tree.maxDepth' Taylor Blau
2020-07-31 21:01 ` Jeff King
2020-07-31 21:22 ` Jeff King
2020-07-31 21:30 ` Taylor Blau
2020-07-31 21:29 ` Taylor Blau
2020-07-31 21:36 ` Jeff King
2020-07-31 21:43 ` Jeff King [this message]
2020-08-03 18:00 ` [PATCH v4 0/3] upload-pack: custom allowed object filters Taylor Blau
2020-08-03 18:00 ` [PATCH v4 2/3] upload-pack.c: allow banning certain object filter(s) Taylor Blau
2020-08-03 18:00 ` [PATCH v4 1/3] list_objects_filter_options: introduce 'list_object_filter_config_name' Taylor Blau
2020-08-03 18:00 ` [PATCH v4 3/3] upload-pack.c: introduce 'uploadpackfilter.tree.maxDepth' Taylor Blau
2020-08-04 0:37 ` [PATCH v4 0/3] upload-pack: custom allowed object filters 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=20200731214311.GB1457058@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=szeder.dev@gmail.com \
/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).