From: rct@gherkin.frus.com (Bob_Tracy)
To: linux-kernel@vger.kernel.org
Cc: axboe@kernel.org
Subject: weird application breakage in 2.5.2-pre5
Date: Thu, 3 Jan 2002 08:49:49 -0600 (CST) [thread overview]
Message-ID: <m16M9Bl-0005kjC@gherkin.frus.com> (raw)
The application is elm2.4.ME+.82 with PGP 6.5.8. Works fine under
kernel version 2.4.17. Under 2.5.2-pre5, when I try to encrypt+sign
a message to a particular recipient for which I have two matching keys
on my pgp keyring, no matching pgp key is found. The *only* difference
between "works" and "doesn't" is the kernel version.
Cranked up the debug level on elm in an attempt to see what's happening,
and at level 41, I notice that the parent (elm) isn't reading anything
from the child (pgp -kv recipient_address). No error indication of any
kind, so fork(), pipe(), execl(), fdopen(), and fgets() all seem to be
happy.
libc version is 2.2.3.
Possible side-effect of bio changes?
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next reply other threads:[~2002-01-03 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 14:49 Bob_Tracy [this message]
2002-01-03 16:26 ` Jens Axboe
2002-01-07 1:48 ` Bob_Tracy
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=m16M9Bl-0005kjC@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=axboe@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®