From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: "Ignacy Kuchciński"
<ignacykuchcinski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: jdl-CYoMK+44s/E@public.gmane.org,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] srcpos: increase MAX_SRCFILE_DEPTH
Date: Wed, 13 Jan 2021 12:06:13 +1100 [thread overview]
Message-ID: <20210113010613.GE435587@yekko.fritz.box> (raw)
In-Reply-To: <CAJq_QG0BHBQYT4RnVi0QSxM_vFK2K-5k1eTpJnwZQtWbKnCBJA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
On Wed, Jan 13, 2021 at 12:13:23AM +0100, Ignacy Kuchciński wrote:
> Some kernels require the MAX_SRCFILE_DEPTH to be bigger than 100,
Wow...
> and
> since it's just a sanity check to detect infinite recursion it shouldn't
> hurt increasing it to 200.
Fair enough, applied.
>
> Signed-off-by: Ignacy Kuchciński <ignacykuchcinski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> srcpos.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/srcpos.c b/srcpos.c
> index f5205fb..4fdb22a 100644
> --- a/srcpos.c
> +++ b/srcpos.c
> @@ -20,7 +20,7 @@ struct search_path {
> static struct search_path *search_path_head, **search_path_tail;
>
> /* Detect infinite include recursion. */
> -#define MAX_SRCFILE_DEPTH (100)
> +#define MAX_SRCFILE_DEPTH (200)
> static int srcfile_depth; /* = 0 */
>
> static char *get_dirname(const char *path)
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-01-13 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 23:13 [PATCH] srcpos: increase MAX_SRCFILE_DEPTH Ignacy Kuchciński
[not found] ` <CAJq_QG0BHBQYT4RnVi0QSxM_vFK2K-5k1eTpJnwZQtWbKnCBJA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-01-13 1:06 ` David Gibson [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210113010613.GE435587@yekko.fritz.box \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ignacykuchcinski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jdl-CYoMK+44s/E@public.gmane.org \
/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.
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).