From: "Kevin D. Kissell" <kevink@mips.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Patches for 34K APRP
Date: Thu, 17 Apr 2008 15:43:02 +0200 [thread overview]
Message-ID: <480753E6.3030402@mips.com> (raw)
In-Reply-To: <20080417132610.GB31453@linux-mips.org>
Ralf Baechle wrote:
> On Wed, Apr 16, 2008 at 03:32:22PM +0200, Kevin D. Kissell wrote:
>
>
>> --- a/arch/mips/kernel/kspd.c
>> +++ b/arch/mips/kernel/kspd.c
>> @@ -257,7 +257,7 @@ void sp_work_handle_request(void)
>>
>> vcwd = vpe_getcwd(tclimit);
>>
>> - /* change to the cwd of the process that loaded the SP program */
>> + /* change to cwd of the process that loaded the SP program */
>> old_fs = get_fs();
>> set_fs(KERNEL_DS);
>> sys_chdir(vcwd);
>> @@ -323,6 +323,9 @@ static void sp_cleanup(void)
>> set >>= 1;
>> }
>> }
>> +
>> + /* Put daemon cwd back to root to avoid umount problems */
>> + sys_chdir("/");
>>
>
> Still not kosher; there might be multiple roots on a system ...
>
What do you suggest, then? Leaving things as they are makes it impossible
to do a clean shutdown of an APRP system if the kspd was last used to
support
an RP binary that was read from a mounted file system. I respectfully
submit
that it's at least an order of magnitude more likely that a mounted file
system
will have been used than a chrooted, mounted file system.
Regards,
Kevin K.
prev parent reply other threads:[~2008-04-17 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 13:32 Patches for 34K APRP Kevin D. Kissell
2008-04-16 13:42 ` Kevin D. Kissell
2008-04-17 12:10 ` Ralf Baechle
2008-04-17 12:29 ` Ralf Baechle
2008-04-17 12:43 ` Ralf Baechle
2008-04-17 13:38 ` Kevin D. Kissell
2008-04-18 9:52 ` Ralf Baechle
2008-04-17 13:26 ` Ralf Baechle
2008-04-17 13:43 ` Kevin D. Kissell [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=480753E6.3030402@mips.com \
--to=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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