From: "Aurélien Aptel" <aaptel@suse.com>
To: Shyam Prasad N <nspmangalore@gmail.com>,
Pavel Shilovsky <piastryyy@gmail.com>,
Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
sribhat.msa@outlook.com
Subject: Re: [PATCH][SMB3] mount.cifs: use SUDO_UID env variable for cruid
Date: Wed, 16 Sep 2020 12:56:51 +0200 [thread overview]
Message-ID: <87r1r2ugzw.fsf@suse.com> (raw)
In-Reply-To: <CANT5p=oiTY63d5yVyywiTrCqpAmvaugMVVpQRV7RT7ZA9HU2+Q@mail.gmail.com>
Shyam Prasad N <nspmangalore@gmail.com> writes:
> This is a fix for the scenario of a krb5 user running a "sudo mount".
> Even if the user has cred cache populated, when the mount is run using
> sudo, uid switches to 0. So cred cache for the root user will be
> searched for, unless cruid is specified explicitly. This fix checks
> for cruid=$SUDO_UID as a fallback option, when the mount fails with
> ENOKEY.
The idea seems good.
> @@ -2053,7 +2066,24 @@ int main(int argc, char **argv)
> parsed_info = NULL;
> fprintf(stderr, "Unable to allocate memory: %s\n",
> strerror(errno));
> - return EX_SYSERR;
> + rc = EX_SYSERR;
> + goto mount_exit;
> + }
> +
> + reinit_parsed_info =
> + (struct parsed_mount_info *) malloc(sizeof(*reinit_parsed_info));
> + if (reinit_parsed_info == NULL) {
> + fprintf(stderr, "Unable to allocate memory: %s\n",
> + strerror(errno));
> + rc = EX_SYSERR;
> + goto mount_exit;
> + }
> +
> + options = calloc(options_size, 1);
> + if (!options) {
> + fprintf(stderr, "Unable to allocate memory.\n");
> + rc = EX_SYSERR;
> + goto mount_exit;
This function later forks, so if you allocate before the fork, you need
to free in parent and in the child.
> @@ -2228,6 +2252,7 @@ mount_retry:
> if (nextaddress)
> *nextaddress++ = '\0';
> }
> + memset(options, 0, sizeof(*options));
> goto mount_retry;
Altho not wrong this is a bit misleading as options is a char*. If you
do a memset do it option_size, or do options[0] = 0;
> case ENODEV:
> fprintf(stderr,
> @@ -2250,6 +2275,21 @@ mount_retry:
> already_uppercased = 1;
> goto mount_retry;
> }
Need to reset options again before goto I guess. Maybe reset option
after the retry label?
> }
> - free(options);
> - free(orgoptions);
> - free(mountpoint);
> + if (reinit_parsed_info)
> + free(reinit_parsed_info);
> + if (options)
> + free(options);
> + if (orgoptions)
> + free(orgoptions);
> + if (mountpoint)
> + free(mountpoint);
> return rc;
free(NULL) is defined to be a no-op, you don't need the checks.
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
next prev parent reply other threads:[~2020-09-16 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 10:00 [PATCH][SMB3] mount.cifs: use SUDO_UID env variable for cruid Shyam Prasad N
2020-09-16 10:56 ` Aurélien Aptel [this message]
2020-09-16 16:17 ` Shyam Prasad N
2020-09-17 8:57 ` Aurélien Aptel
2020-09-17 9:11 ` Shyam Prasad N
2020-09-17 10:13 ` Aurélien Aptel
2020-09-21 3:50 ` Shyam Prasad N
2020-09-21 8:19 ` Aurélien Aptel
2020-11-09 23:43 ` Pavel Shilovsky
2020-11-27 10:24 ` Shyam Prasad N
2020-12-09 19:32 ` Pavel Shilovsky
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=87r1r2ugzw.fsf@suse.com \
--to=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=piastryyy@gmail.com \
--cc=smfrench@gmail.com \
--cc=sribhat.msa@outlook.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 NNTP newsgroup(s).