Re: [Vserver] [Release] Stable 2.2.0
Herbert Poetzl a écrit : Greetings Community! after a longer rc stage, to get rid of all the minor issues, we proudly present the first release of the new stable 2.2 branch, which includes all the 'considered stable' features of the previous devel branch (2.1.x) which has been superceded by the 2.3.x devel branch ... http://www.13thfloor.at/vserver/s_rel26/v2.2.0/ (tools supposed to work fine on Mandriva 2007.x) thanks to all who helped in development and did test the release candidates ... enjoy, Herbert ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver Cool and thanks again for your job Bertl.. i have seen on kernel.org that 2.6.21 is nearly ready... I've tried a 2.6.21-rc5, without patch of course, in a vmware and it works fine. Ready to try new patchs :-) Pmenier ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] CIFS-mounts in vserver guests
Hi Herbert,
Am Freitag, 30. März 2007 schrieb Herbert Poetzl:
cya there then ...
after our conversion I got the quick cifs hack running (using a special
CLONE-flag for the cifs-thread).
The I got this patch, which changes the api to kthread_run. But, the problem
remains. I still got this error in dmesg:
vxW: xid=115 tried to spawn a kernel thread.
CIFS VFS: cifs_mount failed w/return code = -12
The patch works if I try to mount on the host.
Any suggestions?
-
Wilhelm
Index: connect.c
===
--- connect.c (.../2.6.19.1) (revision 20)
+++ connect.c (.../kthread_support) (revision 20)
@@ -30,6 +30,7 @@
#include linux/mempool.h
#include linux/delay.h
#include linux/completion.h
+#include linux/kthread.h
#include linux/pagevec.h
#include asm/uaccess.h
#include asm/processor.h
@@ -119,7 +120,7 @@
struct mid_q_entry * mid_entry;
spin_lock(GlobalMid_Lock);
- if(server-tcpStatus == CifsExiting) {
+ if( kthread_should_stop() ) {
/* the demux thread will exit normally
next time through the loop */
spin_unlock(GlobalMid_Lock);
@@ -181,7 +182,7 @@
spin_unlock(GlobalMid_Lock);
up(server-tcpSem);
- while ((server-tcpStatus != CifsExiting) (server-tcpStatus != CifsGood))
+ while ( (!kthread_should_stop()) (server-tcpStatus != CifsGood))
{
try_to_freeze();
if(server-protocolType == IPV6) {
@@ -198,7 +199,7 @@
} else {
atomic_inc(tcpSesReconnectCount);
spin_lock(GlobalMid_Lock);
- if(server-tcpStatus != CifsExiting)
+ if( !kthread_should_stop() )
server-tcpStatus = CifsGood;
server-sequence_number = 0;
spin_unlock(GlobalMid_Lock);
@@ -344,7 +345,6 @@
int isMultiRsp;
int reconnect;
- daemonize(cifsd);
allow_signal(SIGKILL);
current-flags |= PF_MEMALLOC;
server-tsk = current; /* save process info to wake at shutdown */
@@ -360,7 +360,7 @@
GFP_KERNEL);
}
- while (server-tcpStatus != CifsExiting) {
+ while (!kthread_should_stop()) {
if (try_to_freeze())
continue;
if (bigbuf == NULL) {
@@ -399,7 +399,7 @@
kernel_recvmsg(csocket, smb_msg,
iov, 1, 4, 0 /* BB see socket.h flags */);
- if (server-tcpStatus == CifsExiting) {
+ if ( kthread_should_stop() ) {
break;
} else if (server-tcpStatus == CifsNeedReconnect) {
cFYI(1, (Reconnect after server stopped responding));
@@ -523,7 +523,7 @@
total_read += length) {
length = kernel_recvmsg(csocket, smb_msg, iov, 1,
pdu_length - total_read, 0);
- if((server-tcpStatus == CifsExiting) ||
+ if( kthread_should_stop() ||
(length == -EINTR)) {
/* then will exit */
reconnect = 2;
@@ -756,7 +756,6 @@
GFP_KERNEL);
}
- complete_and_exit(cifsd_complete, 0);
return 0;
}
@@ -1779,10 +1778,11 @@
so no need to spinlock this init of tcpStatus */
srvTcp-tcpStatus = CifsNew;
init_MUTEX(srvTcp-tcpSem);
- rc = (int)kernel_thread((void *)(void *)cifs_demultiplex_thread, srvTcp,
- CLONE_FS | CLONE_FILES | CLONE_VM);
- if(rc 0) {
-rc = -ENOMEM;
+ srvTcp-tsk = kthread_run((void *)(void *)cifs_demultiplex_thread, srvTcp, cifsd);
+ if( IS_ERR(srvTcp-tsk) ) {
+rc = PTR_ERR(srvTcp-tsk);
+cERROR(1,(error %d create cifsd thread, rc));
+srvTcp-tsk = NULL;
sock_release(csocket);
kfree(volume_info.UNC);
kfree(volume_info.password);
@@ -1973,7 +1973,7 @@
spin_unlock(GlobalMid_Lock);
if(srvTcp-tsk) {
send_sig(SIGKILL,srvTcp-tsk,1);
-wait_for_completion(cifsd_complete);
+kthread_stop(srvTcp-tsk);
}
}
/* If find_unc succeeded then rc == 0 so we can not end */
@@ -1987,9 +1987,9 @@
temp_rc = CIFSSMBLogoff(xid, pSesInfo);
/* if the socketUseCount is now zero */
if((temp_rc == -ESHUTDOWN)
- (pSesInfo-server-tsk)) {
+ (pSesInfo-server) (pSesInfo-server-tsk)) {
send_sig(SIGKILL,pSesInfo-server-tsk,1);
- wait_for_completion(cifsd_complete);
+ kthread_stop(pSesInfo-server-tsk);
}
} else
cFYI(1, (No session or bad tcon));
@@ -3273,7 +3273,7 @@
cFYI(1,(Waking up socket by sending it signal));
if(cifsd_task) {
send_sig(SIGKILL,cifsd_task,1);
- wait_for_completion(cifsd_complete);
+ kthread_stop(cifsd_task);
}
rc = 0;
} /* else - we have an smb session
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] [Release] Stable 2.2.0 : where is the changelog?
Hello, Where can I find the change log from version 2.02? I don't see it linked from http://www.13thfloor.at/vserver/s_rel26/v2.2.0/ Thanks! Guillaume Herbert Poetzl a écrit : Greetings Community! after a longer rc stage, to get rid of all the minor issues, we proudly present the first release of the new stable 2.2 branch, which includes all the 'considered stable' features of the previous devel branch (2.1.x) which has been superceded by the 2.3.x devel branch ... http://www.13thfloor.at/vserver/s_rel26/v2.2.0/ (tools supposed to work fine on Mandriva 2007.x) thanks to all who helped in development and did test the release candidates ... enjoy, Herbert ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver -- Guillaume Pratte Recherche et développement Révolution Linux Toutes les opinions et les prises de position exprimées dans ce courriel sont celles de son auteur et ne répresentent pas nécessairement celles de Révolution Linux. Any views and opinions expressed in this email are solely those of the author and do not necessarily represent those of Revolution Linux. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] [Release] Stable 2.2.0 : where is the changelog?
Guillaume Pratte wrote: Hello, Where can I find the change log from version 2.02? I don't see it linked from http://www.13thfloor.at/vserver/s_rel26/v2.2.0/ Thanks! Guillaume AFAIK there is none. In theory, a combination of http://linux-vserver.org/ChangeLog-2.1 and http://linux-vserver.org/ChangeLog-2.2 should get you there, but the first is horribly out of date, so here's a little ChangeLog-according-to-Daniel. The major changes are: - COW link breaking - 2.6.19+ support (i.e. using the mainline namespaces) - capability masking, allowing things like bind9 to run unmodified in guests - artificially advancing idle time, allowing fair sharing of CPU resources among guests - accounting APIs, making it easier to write monitoring programs And a few of the rather minor/less useful changes: - allows raising the bcapabilities of a guest while it's running - virtualized time - the ability to create private guests, that cannot be easily administered from the host - warnings without CONFIG_VSERVER_DEBUG (so Debian users will see them too...) - legacy disabled by default (so util-vserver 0.30.213+ recommended) - privacy for guests, which will hide things from xid 1 - a scheduling monitor -- Daniel Hokka Zakrisson ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Vserver and VRF support
Is there any work done to make Vserver work with VRF? -Albert ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Vserver and VRF support
Albert Mak (almak) wrote: Is there any work done to make Vserver work with VRF? -Albert Meaning multiple routing tables? That's already the recommended way to set different default routes for the guests. Works the same way they do in Linux. -- Daniel Hokka Zakrisson ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] CIFS-mounts in vserver guests: solved
Am Montag, 2. April 2007 schrieb Wilhelm Meier: after our conversion I got the quick cifs hack running (using a special CLONE-flag for the cifs-thread). The I got this patch, which changes the api to kthread_run. But, the problem remains. I still got this error in dmesg: I've to correct myself! I had a configuration flaw ... if the patch is in place, it works as expected. CIFS-shares can be mounted inside the guests. - Wilhelm ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
