Msg05658.html: Difference between revisions
From Linix VServer
Jump to navigationJump to search
(Restored content from Wayback Machine) |
(No difference)
|
Latest revision as of 23:06, 10 November 2025
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Vserver] SMP oops 2.4.23 v1.22[edit]
- From: Herbert Poetzl
- Date: Sat, 20 Dec 2003 03:28:17 +0100 (CET)
Hi! just wanted to find out how far the rabbit hole goes ... browsing the source, I found the folowing locations for possible s_info races ... forget_original_parent() goodness() schedule() update_process_times() vc_new_s_context() and of course similar is true for ip_info :( there are two 'general' solutions to this issue, besides the obvious one (adding tons of lock/unlock pairs) * replace alloc/dealloc with get/put and change if (x->s_info) ... to if (.._get(x->s_info)) * add a dummy s_info/ip_info for the host context (this can result in data corruption) so I guess we are going for the get/put approach best, Herbert
- References:
- [Vserver] SMP oops 2.4.23 v1.22
- From: nathan
- Re: [Vserver] SMP oops 2.4.23 v1.22
- From: Herbert Poetzl
- [Vserver] SMP oops 2.4.23 v1.22
- Prev by Date: Re: [Vserver] Re: [parisc-linux] syscall number for vserver
- Next by Date: [Vserver] creating vservers
- Previous by thread: Re: [Vserver] SMP oops 2.4.23 v1.22
- Next by thread: [Vserver] Business Services
- Index(es):