From: Arjan van de Ven <arjanv@redhat.com>
To: "Zach, Yoav" <yoav.zach@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Handle non-readable binfmt_misc executables
Date: Sun, 20 Jun 2004 12:50:25 +0200 [thread overview]
Message-ID: <20040620105025.GA9349@devserv.devel.redhat.com> (raw)
In-Reply-To: <2C83850C013A2540861D03054B478C060416BC17@hasmsx403.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
On Sun, Jun 20, 2004 at 01:41:30PM +0300, Zach, Yoav wrote:
> I'm not sure I understand the problem. Load_elf_binary also
> uses sys_close for recovery in case of error. Can you please
> give me more details on the problems you see with using sys_close ?
for one, sys_close, while currently exported, shouldn't be really.
(it is exported right now for a few drivers that have invalid firmware
loaders that haven't been converted to the firmware loading framework).
In addition it's way overkill, you created the fd so half the safety
precautions shouldn/t be needed
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-20 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 10:41 [PATCH] Handle non-readable binfmt_misc executables Zach, Yoav
2004-06-20 10:50 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 9:54 [PATCH] Handle non-readable binfmt misc executables Zach, Yoav
2004-06-22 7:58 [PATCH] Handle non-readable binfmt_misc executables Zach, Yoav
2004-06-21 11:31 [PATCH] Handle non-readable binfmt misc executables Zach, Yoav
2004-06-21 11:49 ` Albert Cahalan
[not found] <2C83850C013A2540861D03054B478C060416BC0E@hasmsx403.ger.corp.intel.com>
2004-06-20 12:17 ` Albert Cahalan
[not found] <200406181612.i5IGCIYY001854@hera.kernel.org>
2004-06-19 14:38 ` [PATCH] Handle non-readable binfmt_misc executables Arjan van de Ven
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=20040620105025.GA9349@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yoav.zach@intel.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