From: Gao Xiang <xiang@kernel.org>
To: Lucas Karpinski <lkarpinski@nvidia.com>
Cc: lasyaprathipati@gmail.com, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH v2] erofs-utils: lib: fix potential NULL pointer dereference in docker_config.c
Date: Wed, 18 Mar 2026 22:54:11 +0800 [thread overview]
Message-ID: <abq8f00vvrywkf7R@debian> (raw)
In-Reply-To: <6f2045fe-9ed2-462f-8a95-54575e75311e@nvidia.com>
Hi Lucus,
On Wed, Mar 18, 2026 at 10:26:08AM -0400, Lucas Karpinski wrote:
> On 2026-03-18 10:06 a.m., Lucas Karpinski wrote:
> > On 2026-03-16 4:53 a.m., lasyaprathipati@gmail.com wrote:
> >> From: Sri Lasya <lasyaprathipati@gmail.com>
> >>
> >> ---
> >> lib/remotes/docker_config.c | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/lib/remotes/docker_config.c b/lib/remotes/docker_config.c
> >> index b346ee8..6401c1b 100644
> >> --- a/lib/remotes/docker_config.c
> >> +++ b/lib/remotes/docker_config.c
> >> @@ -202,8 +202,10 @@ int erofs_docker_config_lookup(const char *registry,
> >> }
> >>
> >> entry = json_object_iter_peek_value(&it);
> >> - if (!entry)
> >> + if (!entry) {
> >> + json_object_iter_next(&it);
> >> continue;
> >> + }
> >> if (json_object_object_get_ex(entry, "auth", &auth_field)) {
> >> b64 = json_object_get_string(auth_field);
> >> if (b64 && *b64) {
> > There's still a tab issue as Gao mentioned in v1. This looks like a diff
> > from your v1 to your v2 patch. Similarly, you also dropped your
> > Signed-Off and are now using a From.
> >
> > Lastly, you submitted another patch just yesterday that includes this
> > change in addition to other changes. It is very difficult to follow what
> > you're doing.
>
> One correction, no tab issue anymore.
Thanks for reply and help.
As you may noticed, this year EROFS became a GSOC organization,
so there are many new students sending patches and proposal
these days.
Of course, it's a good thing since we could get more new
developers. But one thing that I'm not quite sure if they are
really humans or AI-assisted bots, taking a simple example:
As you may noticed, this thread Cc an email <gaoxiang25@kernel.org>
which is never existed (my email is xiang@kernel.org or a very
very old gaoxiang25@huawei.com one but it never works for many
years since I changed my job many years ago.
also
Another thread I've seen <yifan.yfzhao@linux.dev>, which is
never existed either.
https://lore.kernel.org/r/CAGSu4WMGStFw7DzePCDW0JKM4DFeia4oj_U1PMDz=kG4hdLEaQ@mail.gmail.com
I'm not sure if they are AI hallucination or not, but they really
warns me that I should take those GSoC proposals more carefully.
Of course, those patches can be still valid, but I need to
review more carefully in case of potential random AI hallucination
or meaningless changes.
Thanks,
Gao Xiang
>
prev parent reply other threads:[~2026-03-18 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 8:53 [PATCH v2] erofs-utils: lib: fix potential NULL pointer dereference in docker_config.c lasyaprathipati
2026-03-18 13:22 ` Utkal Singh
2026-03-18 14:06 ` Lucas Karpinski
2026-03-18 14:26 ` Lucas Karpinski
2026-03-18 14:54 ` Gao Xiang [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=abq8f00vvrywkf7R@debian \
--to=xiang@kernel.org \
--cc=lasyaprathipati@gmail.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=lkarpinski@nvidia.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.