From: Daniel Kiper <dkiper@net-space.pl>
To: Qiumiao Zhang <zhangqiumiao1@huawei.com>
Cc: grub-devel@gnu.org, fengtao40@huawei.com, yanan@huawei.com
Subject: Re: [PATCH] util/grub-mount: Check file path sanity
Date: Wed, 25 Oct 2023 14:14:38 +0200 [thread overview]
Message-ID: <20231025121438.rxahlnen6muxypvs@tomti.i.net-space.pl> (raw)
In-Reply-To: <20231025035457.1342-1-zhangqiumiao1@huawei.com>
On Wed, Oct 25, 2023 at 11:54:57AM +0800, Qiumiao Zhang via Grub-devel wrote:
> In grub-mount.c, the function argp_parser() lacks a check on the sanity of the
> file path when parsing parameters. This results in a segmentation fault if a
> partition is mounted to a non-existent path.
>
> Signed-off-by: Qiumiao Zhang <zhangqiumiao1@huawei.com>
Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
Daniel
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
prev parent reply other threads:[~2023-10-25 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 3:54 [PATCH] util/grub-mount: Check file path sanity Qiumiao Zhang via Grub-devel
2023-10-25 12:14 ` Daniel Kiper [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=20231025121438.rxahlnen6muxypvs@tomti.i.net-space.pl \
--to=dkiper@net-space.pl \
--cc=fengtao40@huawei.com \
--cc=grub-devel@gnu.org \
--cc=yanan@huawei.com \
--cc=zhangqiumiao1@huawei.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 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).