From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
git@vger.kernel.org, ZhenTian <loooseleaves@gmail.com>
Subject: Re: [PATCHv3] gpg-interface: check gpg signature creation status
Date: Tue, 14 Jun 2016 18:26:33 -0400 [thread overview]
Message-ID: <20160614222633.GA32020@sigill.intra.peff.net> (raw)
In-Reply-To: <20160614215019.GB22334@sigill.intra.peff.net>
On Tue, Jun 14, 2016 at 05:50:19PM -0400, Jeff King wrote:
> On Tue, Jun 14, 2016 at 11:13:54AM -0700, Junio C Hamano wrote:
>
> > Michael J Gruber <git@drmicha.warpmail.net> writes:
> >
> > > bottom = signature->len;
> > > - len = strbuf_read(signature, gpg.out, 1024);
> > > + strbuf_read(signature, gpg.out, 1024);
> > > + strbuf_read(&err, gpg.err, 0);
> >
> > Hmmmm, isn't this asking for a deadlock? When GPG spews more than
> > what would fit in a pipe buffer to its standard error (hence gets
> > blocked), its standard output may not complete, and the we would get
> > stuck by attempting to read from gpg.out, failing to reach the other
> > strbuf_read() that would unblock GPG by reading from gpg.err?
>
> Yeah, it definitely is a deadlock. I think we'd need a select loop to
> read into multiple strbufs at once (we can't use "struct async" because
> that might happen in another process).
Something like this on top of Michael's patch (only lightly tested).
I'm still undecided on whether it is a better approach than making sure
the stdout we got looks sane. In particular I'd worry that it would make
things harder for somebody trying to plug in something gpg-like (e.g.,
if you wanted to do something exotic like call a program which fetched
the signature from a remote device or something). But it's probably not
_that_ hard for such a script to emulate --status-fd.
---
diff --git a/gpg-interface.c b/gpg-interface.c
index 850dc81..576e462 100644
--- a/gpg-interface.c
+++ b/gpg-interface.c
@@ -153,6 +153,7 @@ int sign_buffer(struct strbuf *buffer, struct strbuf *signature, const char *sig
const char *args[5];
size_t i, j, bottom;
struct strbuf err = STRBUF_INIT;
+ struct strbuf_reader readers[2];
gpg.argv = args;
gpg.in = -1;
@@ -183,8 +184,15 @@ int sign_buffer(struct strbuf *buffer, struct strbuf *signature, const char *sig
close(gpg.in);
bottom = signature->len;
- strbuf_read(signature, gpg.out, 1024);
- strbuf_read(&err, gpg.err, 0);
+
+ readers[0].buf = signature;
+ readers[0].fd = gpg.out;
+ readers[0].hint = 1024;
+ readers[1].buf = &err;
+ readers[1].fd = gpg.err;
+ readers[1].hint = 1024;
+ strbuf_read_parallel(readers, 2);
+
close(gpg.out);
close(gpg.err);
diff --git a/strbuf.c b/strbuf.c
index 1ba600b..f674b23 100644
--- a/strbuf.c
+++ b/strbuf.c
@@ -395,6 +395,58 @@ ssize_t strbuf_read_once(struct strbuf *sb, int fd, size_t hint)
return cnt;
}
+void strbuf_read_parallel(struct strbuf_reader *readers, int nr)
+{
+ int i;
+ struct pollfd *pfd;
+
+ ALLOC_ARRAY(pfd, nr);
+ for (i = 0; i < nr; i++)
+ readers[i].error = 0;
+
+ while (1) {
+ int pollsize = 0;
+ int ret;
+
+ for (i = 0; i < nr; i++) {
+ if (readers[i].fd < 0)
+ continue;
+ pfd[pollsize].fd = readers[i].fd;
+ pfd[pollsize].events = POLLIN;
+ readers[i].pfd = &pfd[pollsize];
+ pollsize++;
+ }
+
+ if (!pollsize)
+ break;
+
+ ret = poll(pfd, pollsize, -1);
+ if (ret < 0) {
+ if (errno == EINTR)
+ continue;
+ /* should never happen? */
+ die_errno("poll failed");
+ }
+
+ for (i = 0; i < nr; i++) {
+ if (readers[i].fd < 0)
+ continue;
+ if (readers[i].pfd->revents &
+ (POLLIN|POLLHUP|POLLERR|POLLNVAL)) {
+ ret = strbuf_read_once(readers[i].buf,
+ readers[i].fd,
+ readers[i].hint);
+ if (ret < 0)
+ readers[i].error = errno;
+ if (ret <= 0)
+ readers[i].fd = -1;
+ }
+ }
+ }
+
+ free(pfd);
+}
+
ssize_t strbuf_write(struct strbuf *sb, FILE *f)
{
return sb->len ? fwrite(sb->buf, 1, sb->len, f) : 0;
diff --git a/strbuf.h b/strbuf.h
index 7987405..b93822e 100644
--- a/strbuf.h
+++ b/strbuf.h
@@ -374,6 +374,25 @@ extern ssize_t strbuf_read(struct strbuf *, int fd, size_t hint);
*/
extern ssize_t strbuf_read_once(struct strbuf *, int fd, size_t hint);
+/**
+ * Read from several descriptors in parallel, each into its own strbuf.
+ * This can be used, for example, to capture stdout and stderr from a
+ * sub-process without worrying about deadlocks.
+ */
+struct strbuf_reader {
+ /* Initialized by caller */
+ struct strbuf *buf;
+ int fd;
+ size_t hint;
+
+ /* Returned by strbuf_read_parallel */
+ int error; /* 0 for success, otherwise errno */
+
+ /* Internal use */
+ struct pollfd *pfd;
+};
+void strbuf_read_parallel(struct strbuf_reader *readers, int nr);
+
/**
* Read the contents of a file, specified by its path. The third argument
* can be used to give a hint about the file size, to avoid reallocs.
next prev parent reply other threads:[~2016-06-14 22:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 7:50 I lost my commit signature ZhenTian
2016-06-14 7:58 ` Jeff King
2016-06-14 8:09 ` ZhenTian
2016-06-14 8:18 ` Jeff King
2016-06-14 8:39 ` ZhenTian
2016-06-14 9:41 ` Jeff King
2016-06-14 9:56 ` ZhenTian
2016-06-14 10:57 ` Michael J Gruber
2016-06-14 11:11 ` [PATCH] gpg-interface: check gpg signature for correct header Michael J Gruber
2016-06-14 11:20 ` Jeff King
2016-06-14 11:34 ` Michael J Gruber
2016-06-14 11:58 ` Michael J Gruber
2016-06-14 12:05 ` [PATCHv2] " Michael J Gruber
2016-06-14 14:44 ` [PATCHv3] gpg-interface: check gpg signature creation status Michael J Gruber
2016-06-14 18:13 ` Junio C Hamano
2016-06-14 21:50 ` Jeff King
2016-06-14 22:26 ` Jeff King [this message]
2016-06-14 23:47 ` Junio C Hamano
2016-06-15 0:56 ` Jeff King
2016-06-15 7:17 ` Michael J Gruber
2016-06-16 9:25 ` Jeff King
2016-06-16 11:30 ` Michael J Gruber
2016-06-15 3:28 ` Jeff King
2016-06-15 4:27 ` I lost my commit signature ZhenTian
2016-06-15 4:34 ` Jeff King
2016-06-15 7:07 ` Michael J Gruber
2016-06-15 10:36 ` ZhenTian
2016-06-16 7:34 ` Jeff King
2016-06-16 17:06 ` Junio C Hamano
2016-06-17 8:18 ` Michael J Gruber
2016-06-17 16:39 ` Junio C Hamano
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=20160614222633.GA32020@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=loooseleaves@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.
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).