From: Andreas Schwab <schwab@suse.de>
To: Olaf Hering <olh@suse.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: /bin/ls: cannot read symbolic link /proc/$$/exe: Permission denied
Date: Tue, 17 Aug 2004 10:50:15 +0200 [thread overview]
Message-ID: <jept5q9mig.fsf@sykes.suse.de> (raw)
In-Reply-To: <20040817052302.GA11448@suse.de> (Olaf Hering's message of "Tue, 17 Aug 2004 07:23:02 +0200")
Olaf Hering <olh@suse.de> writes:
>> > A better one, clear both new fields, just in case.
>>
>> memset?
>
> perhaps too expensive, no idea.
I don't think that this part of compat_do_execve is exactly time critical.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-08-17 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 13:37 /bin/ls: cannot read symbolic link /proc/$$/exe: Permission denied Olaf Hering
2004-08-16 22:19 ` Olaf Hering
2004-08-16 22:39 ` Olaf Hering
2004-08-16 23:34 ` Andreas Schwab
2004-08-17 5:23 ` Olaf Hering
2004-08-17 8:50 ` Andreas Schwab [this message]
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=jept5q9mig.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
/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