From: David Howells <dhowells@redhat.com>
To: "Alexander Beregalov" <a.beregalov@gmail.com>
Cc: dhowells@redhat.com, jmorris@namei.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] CRED: Further fix execve error handling
Date: Wed, 20 Aug 2008 16:07:26 +0100 [thread overview]
Message-ID: <24497.1219244846@redhat.com> (raw)
In-Reply-To: <a4423d670808200721i3e9add4cn216da7991f0616f3@mail.gmail.com>
Alexander Beregalov <a.beregalov@gmail.com> wrote:
> David, I applied this patch and got the following.
> Is it a different problem?
> I think it is. If yes I will create another topic.
It doesn't look like it's anything to do with my patches. I'd guess the TTY
patches from Alan Cox are the culprit.
David
next prev parent reply other threads:[~2008-08-20 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 13:56 [PATCH] CRED: Further fix execve error handling David Howells
2008-08-20 14:21 ` Alexander Beregalov
2008-08-20 15:07 ` David Howells [this message]
2008-08-20 16:33 ` Alan Cox
2008-08-20 22:37 ` James Morris
2008-08-21 12:43 ` David Howells
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=24497.1219244846@redhat.com \
--to=dhowells@redhat.com \
--cc=a.beregalov@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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