colinux-users — coLinux users mailing list

[coLinux-users] Debugging kernel modules

[deneme.true <den...@gm...>]

Hello,

It is possible to debug kernel modules with indicating 'debug'
paramater to uml at specified this address:

http://user-mode-linux.sourceforge.net/old/debugging.html

Is it possible to debug kernel modules with coLinux? Is it possible to
provide configured debug vmlinux kernels for slow machines?

Thanks in advance.

Re: [coLinux-users] kernel module programming

[yin s. <sun...@gm...>]

are you able to build the colinux kernel and its modules? (./configure; make)
I think this is the way to verify your build environment is properly setup.
then you can try to modify one of the modules, for example comouse.c
after these practice, you should be able to figure what is wrong for
your own module.

/sunyin

On Wed, Apr 18, 2012 at 11:11 AM, deneme.true <den...@gm...> wrote:
> I've prepared the kernel module programming environment as specified
> at this link:
> http://colinux.wikia.com/wiki/CoLinux_FAQ#Q38._Howto_get_kernel_headers_for_coLinux_to_build_an_additional_module.3F
>
> Even, it is not possible to compile a simple hello world module:
> This is hello world sample:
> http://www.faqs.org/docs/kernel/x145.html
>
> And this is Makefile:
> -------------------------------------------------------------------------------------------------------------
> obj-m += hello.o
>
> all:
>        make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
>
> clean:
>        make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean
> --------------------------------------------------------------------------------------------------------------
>
> And this is the error:
>
> make -C /lib/modules/2.6.33.7-co-0.7.9/build M=/root/hello_world modules
> make[1]: Entering directory `/home/m/build/linux-2.6.33.7-build'
> make -C /home/m/build/linux-2.6.33.7-source
> O=/home/m/build/linux-2.6.33.7-build/. modules
>
>
> WARNING: Symbol version dump
> /home/m/build/linux-2.6.33.7-build/Module.symvers           is
> missing; modules will have no dependencies and modversions.
>
>
> CC [M]  /root/hello_world/hello.o
> Building modules, stage 2.
> MODPOST 1 modules
>
> /bin/sh: scripts/mod/modpost: not found
> make[4]: *** [__modpost] Error 127
> make[3]: *** [modules] Error 2
> make[2]: *** [sub-make] Error 2
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/m/build/linux-2.6.33.7-build'
> make: *** [all] Error 2
>
> ------------------------------------------------------------------------------------------------
>
> It is same error.
>
> Probably, prepared kernel module environment doesn't fully functional.
>
> What can I do?
>
> Thanks in advance.
>
>
> 2012/4/18, Paolo Minazzi <pao...@gm...>:
>> If you are able to build a normal kernel module, you will be able to build
>> a module under colinux.
>> You only need to point to the header.
>> I do not remember if you need to use the header in the build/....source
>> folder.
>> Nothing different.
>> Paolo
>>
>>
>> On Tue, Apr 17, 2012 at 7:42 PM, deneme.true <den...@gm...> wrote:
>>
>>> I am trying to compile a kernel module for coLinux and I get /"bin/sh:
>>> scripts/mod/modpost: not found" error.
>>>
>>> As mentioned this thread:
>>>
>>> http://old.nabble.com/-Q--Building-additional-kernel-module-td4769274.html
>>>
>>> I couldn't find "conf/linux-config" kernel config file.
>>>
>>> Also I try this QA 38:
>>>
>>> http://colinux.wikia.com/wiki/CoLinux_FAQ#Q38._Howto_get_kernel_headers_for_coLinux_to_build_an_additional_module.3F
>>>
>>> At this website:
>>>
>>> http://translate.google.com/translate?sl=zh-CN&tl=en&js=n&prev=_t&hl=tr&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fblog.csdn.net%2Fsabalol%2Farticle%2Fdetails%2F2076610
>>>
>>> I must execute "make scripts" command to create modpost but before
>>> executing "make scripts" command, kernel config file should be
>>> generated.
>>>
>>> Is there any method for coLinux without configuring kernel(or with
>>> default values)? because it takes a lot of time and it is possible to
>>> make errors when configuring kernel.
>>>
>>> Thanks in Advance.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Better than sec? Nothing is better than sec when it comes to
>>> monitoring Big Data applications. Try Boundary one-second
>>> resolution app monitoring today. Free.
>>> http://p.sf.net/sfu/Boundary-dev2dev
>>> _______________________________________________
>>> coLinux-users mailing list
>>> coL...@li...
>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>
>>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] kernel module programming

[deneme.true <den...@gm...>]

I've prepared the kernel module programming environment as specified
at this link:
http://colinux.wikia.com/wiki/CoLinux_FAQ#Q38._Howto_get_kernel_headers_for_coLinux_to_build_an_additional_module.3F

Even, it is not possible to compile a simple hello world module:
This is hello world sample:
http://www.faqs.org/docs/kernel/x145.html

And this is Makefile:
-------------------------------------------------------------------------------------------------------------
obj-m += hello.o

all:
	make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules

clean:
	make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean
--------------------------------------------------------------------------------------------------------------

And this is the error:

make -C /lib/modules/2.6.33.7-co-0.7.9/build M=/root/hello_world modules
make[1]: Entering directory `/home/m/build/linux-2.6.33.7-build'
make -C /home/m/build/linux-2.6.33.7-source
O=/home/m/build/linux-2.6.33.7-build/. modules


WARNING: Symbol version dump
/home/m/build/linux-2.6.33.7-build/Module.symvers           is
missing; modules will have no dependencies and modversions.


CC [M]  /root/hello_world/hello.o
Building modules, stage 2.
MODPOST 1 modules

/bin/sh: scripts/mod/modpost: not found
make[4]: *** [__modpost] Error 127
make[3]: *** [modules] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/m/build/linux-2.6.33.7-build'
make: *** [all] Error 2

------------------------------------------------------------------------------------------------

It is same error.

Probably, prepared kernel module environment doesn't fully functional.

What can I do?

Thanks in advance.


2012/4/18, Paolo Minazzi <pao...@gm...>:
> If you are able to build a normal kernel module, you will be able to build
> a module under colinux.
> You only need to point to the header.
> I do not remember if you need to use the header in the build/....source
> folder.
> Nothing different.
> Paolo
>
>
> On Tue, Apr 17, 2012 at 7:42 PM, deneme.true <den...@gm...> wrote:
>
>> I am trying to compile a kernel module for coLinux and I get /"bin/sh:
>> scripts/mod/modpost: not found" error.
>>
>> As mentioned this thread:
>>
>> http://old.nabble.com/-Q--Building-additional-kernel-module-td4769274.html
>>
>> I couldn't find "conf/linux-config" kernel config file.
>>
>> Also I try this QA 38:
>>
>> http://colinux.wikia.com/wiki/CoLinux_FAQ#Q38._Howto_get_kernel_headers_for_coLinux_to_build_an_additional_module.3F
>>
>> At this website:
>>
>> http://translate.google.com/translate?sl=zh-CN&tl=en&js=n&prev=_t&hl=tr&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fblog.csdn.net%2Fsabalol%2Farticle%2Fdetails%2F2076610
>>
>> I must execute "make scripts" command to create modpost but before
>> executing "make scripts" command, kernel config file should be
>> generated.
>>
>> Is there any method for coLinux without configuring kernel(or with
>> default values)? because it takes a lot of time and it is possible to
>> make errors when configuring kernel.
>>
>> Thanks in Advance.
>>
>>
>> ------------------------------------------------------------------------------
>> Better than sec? Nothing is better than sec when it comes to
>> monitoring Big Data applications. Try Boundary one-second
>> resolution app monitoring today. Free.
>> http://p.sf.net/sfu/Boundary-dev2dev
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>

Re: [coLinux-users] kernel module programming

[yin s. <sun...@gm...>]

you need to follow the instructions in doc/building.txt to see how the
kernel is patched for colinux.

On Tue, Apr 17, 2012 at 10:42 AM, deneme.true <den...@gm...> wrote:
> I am trying to compile a kernel module for coLinux and I get /"bin/sh:
> scripts/mod/modpost: not found" error.
>
> As mentioned this thread:
>
> http://old.nabble.com/-Q--Building-additional-kernel-module-td4769274.html
>
> I couldn't find "conf/linux-config" kernel config file.
>
> Also I try this QA 38:
> http://colinux.wikia.com/wiki/CoLinux_FAQ#Q38._Howto_get_kernel_headers_for_coLinux_to_build_an_additional_module.3F
>
> At this website:
> http://translate.google.com/translate?sl=zh-CN&tl=en&js=n&prev=_t&hl=tr&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fblog.csdn.net%2Fsabalol%2Farticle%2Fdetails%2F2076610
>
> I must execute "make scripts" command to create modpost but before
> executing "make scripts" command, kernel config file should be
> generated.
>
> Is there any method for coLinux without configuring kernel(or with
> default values)? because it takes a lot of time and it is possible to
> make errors when configuring kernel.
>
> Thanks in Advance.
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] kernel module programming

[deneme.true <den...@gm...>]

I am trying to compile a kernel module for coLinux and I get /"bin/sh:
scripts/mod/modpost: not found" error.

As mentioned this thread:

http://old.nabble.com/-Q--Building-additional-kernel-module-td4769274.html

I couldn't find "conf/linux-config" kernel config file.

Also I try this QA 38:
http://colinux.wikia.com/wiki/CoLinux_FAQ#Q38._Howto_get_kernel_headers_for_coLinux_to_build_an_additional_module.3F

At this website:
http://translate.google.com/translate?sl=zh-CN&tl=en&js=n&prev=_t&hl=tr&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fblog.csdn.net%2Fsabalol%2Farticle%2Fdetails%2F2076610

I must execute "make scripts" command to create modpost but before
executing "make scripts" command, kernel config file should be
generated.

Is there any method for coLinux without configuring kernel(or with
default values)? because it takes a lot of time and it is possible to
make errors when configuring kernel.

Thanks in Advance.

Re: [coLinux-users] Problem with ptrace protection in Ubuntu

[Alexander K. <Ale...@Kr...>]

Just because I just read an article about the upcoming Linux kernel 3.4,
I wanted to mention that Yama now made it into the kernel main line:

http://heise.de/-1498405 (in German)

https://lkml.org/lkml/2012/3/20/510

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=2d514487faf188938a4ee4fb3464eeecfbdcf8eb



Alexander Kriegisch, 03.02.2012 14:37:
> Thanks Yin for testing this and trying to help me.
> 
> Probably you mean either reptyr or retty when you mention that you
> tested this on your system (I do not know a tool named rettyer).
> 
> I do not know about Debian 6.0.3, but I guess it does not have yama in
> its original kernel so there is no damage done if colinux does not have
> it either. Debian 6.0.3 just does not expect it. so the test is kind of
> pointless. Let me explain (again) why: I am running Ubuntu 11.10. Its
> original kernel *does* have yama, so the rest of the system expects it
> to exist. Probably it checks the return value of
> /proc/sys/kernel/yama/ptrace_scope, but that "file" does not exist if
> there is no yama. Now reptyr even knows about yama, showing a warning
> message if /proc/sys/kernel/yama/ptrace_scope returns 1. As soon as I
> set it to 0 on my native Ubuntu, reptyr works nicely. I guess it also
> does on colinux if you use an OS which does not expect yama ptrace
> protection to be in the kernel, e.g. an older Ubuntu or probably your
> Debian 6.0.3.
> 
> Do you understand the issue at hand now? I hope I made myself clearer
> now. Maybe you have a clue for me. Is there a way to simulate this
> "file" /proc/sys/kernel/yama/ptrace_scope and make it always return 0 so
> Ubuntu and reptyr are satisfied?
> 
> Thanks again
> --
> Alexander
> 
> 
> yin sun, 03.02.2012 06:47:
>> OK, I tried on my debian 6.0.3 (latest colinux kernel), rettyer works.
>> And I am sure the colinux doesn't have yama. whether have yama or not
>> may not be your problem.
>> Since it only provide protection for non root user.
>> not sure what else could be wrong, sorry can't help you more.
>>
>> /Yin
>>
>>
>>
>> On Thu, Feb 2, 2012 at 6:28 PM, yin sun <sun...@gm...> wrote:
>>> I guess you are right, there is no yama LSM in 2.6.33.7
>>>
>>> /Yin
>>>
>>> On Tue, Jan 31, 2012 at 8:48 PM, Alexander Kriegisch
>>> <kri...@fr...> wrote:
>>>> Hi.
>>>>
>>>> I am running andLinux/coLinux:
>>>>
>>>> $ uname -a
>>>> Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux
>>>>
>>>> But...
>>>>
>>>> $ cat /etc/motd | head -n 1
>>>> Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)
>>>>
>>>> Now the problem is so-called "ptrace protection", explained there:
>>>> https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection
>>>>
>>>> I tried to use tools like reptyr and injcode:
>>>> https://github.com/nelhage/reptyr#readme
>>>> https://github.com/ThomasHabets/injcode#readme
>>>>
>>>> Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel (without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.
>>>>
>>>> My questions are:
>>>>  1) Can you confirm that my suscpcion is correct?
>>>>    2a) If not, what else might be the reason for my problems?
>>>>    2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support from somewhere or asking you to build in yama protection in the future?
>>>>
>>>> Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.
>>>>
>>>> Any help is appreciated. Thanks in advance.
> 
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 

Re: [coLinux-users] Crashing problem

[Lorne S. <dr...@sh...>]

On 03/26/2012 02:48 PM, Henry N. wrote:
> Hello Lorne,
> 
> please go into source code and get the file doc/debugging. There is written how to analyse the windows crash dumps. We need the stack backtrace. After you have such, please attach it on a new created bug report on sourceforge.
> Please also attach your configuration.
> 
> 5-10% is not often. More reproducing would be better. Maybe play with the options. Try less memory, try the initrd. So other developer can also reproduce this bug.

I've created a bug report for this crash.  It's bug 3512516.  Let me
know if there's anything else you require to help track this down.  This
is very high priority for me right now, so I'll be able to help with
this as much as I can.

-- 
Lorne Sturtevant
Sum Ergo Cogito

Re: [coLinux-users] Crashing problem

[Lorne S. <dr...@sh...>]

On 03/26/2012 02:48 PM, Henry N. wrote:
> Hello Lorne,
> 
> please go into source code and get the file doc/debugging. There is written how to analyse the windows crash dumps. We need the stack backtrace. After you have such, please attach it on a new created bug report on sourceforge.
> Please also attach your configuration.
> 
> 5-10% is not often. More reproducing would be better. Maybe play with the options. Try less memory, try the initrd. So other developer can also reproduce this bug.

I'll start there.  From what I understand though, crash dumps will only
be produced when the crash is a blue screen, not a reboot.  Is that
correct?  Only <5% of my crashes are blue screens.  Rebooting is far far
more likely.

-- 
Lorne Sturtevant
Sum Ergo Cogito

Re: [coLinux-users] Crashing problem

[Henry N. <hen...@ar...>]

Hello Lorne,

please go into source code and get the file doc/debugging. There is written how to analyse the windows crash dumps. We need the stack backtrace. After you have such, please attach it on a new created bug report on sourceforge.
Please also attach your configuration.

5-10% is not often. More reproducing would be better. Maybe play with the options. Try less memory, try the initrd. So other developer can also reproduce this bug.
-- 
Henry N.

-Urspr. Mitteilung-
Betreff: [coLinux-users] Crashing problem
Von: Lorne Sturtevant <dr...@sh...>
Datum: 26.03.2012 21:53

I've been having a problem with coLinux crashing on me.  The crash
happens as soon as I start coLinux, but it only happens about 5%-10% of
the time.  I'm running coLinux on WinXP SP3.  When it crashes, it most
often just reboots the host PC.  Very rarely it will blue screen instead.

I've done some searching on the mailing list already and found some
posts about PAE causing a problem.  I did some experiments and I can get
coLinux to start without crashing by turning PAE off.  If I boot Windows
with the parameters /nopae /noexecute=alwaysoff, then I can't reproduce
the crash.  I've also experimented with the other parameters to
/noexecute, but alwaysoff is the only one that works since it's the only
one that truely disables PAE.

Unfortunately, I cannot run the system with PAE off.  I need PAE on so
DEP is enabled.  So my questions are: Is it possible to run with PAE on?
 Is there any other things I can try try and fix the crash?  I'm willing
to get into the code to try and track down this bug and fix it.  Where
should I get started?

-- 
Lorne Sturtevant
Sum Ergo Cogito

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] Crashing problem

[Lorne S. <dr...@sh...>]

I've been having a problem with coLinux crashing on me.  The crash
happens as soon as I start coLinux, but it only happens about 5%-10% of
the time.  I'm running coLinux on WinXP SP3.  When it crashes, it most
often just reboots the host PC.  Very rarely it will blue screen instead.

I've done some searching on the mailing list already and found some
posts about PAE causing a problem.  I did some experiments and I can get
coLinux to start without crashing by turning PAE off.  If I boot Windows
with the parameters /nopae /noexecute=alwaysoff, then I can't reproduce
the crash.  I've also experimented with the other parameters to
/noexecute, but alwaysoff is the only one that works since it's the only
one that truely disables PAE.

Unfortunately, I cannot run the system with PAE off.  I need PAE on so
DEP is enabled.  So my questions are: Is it possible to run with PAE on?
 Is there any other things I can try try and fix the crash?  I'm willing
to get into the code to try and track down this bug and fix it.  Where
should I get started?

-- 
Lorne Sturtevant
Sum Ergo Cogito

Re: [coLinux-users] 64bit support

[Lorne S. <lst...@us...>]

On 03/12/2012 11:16 AM, Jun Li wrote:
> I have asked for 64-bit coLinux for years but did not get any progress.
> I guess it is time for the dev team to make it higher priority now.
> 
> 

We don't just want someone to do it on their own time.  We'll pay
someone to complete the port.


-- 
Lorne Sturtevant
Senior Programmer
Userful Corporation (GMT -7)
Tel: +1.403-235-5343 | Fax: +1.403-206-7010 | Skype: lorne.sturtevant
Suite 200, 709 11th Ave. SW, Calgary, AB, T2R 0E3 CANADA
Manage & Multiply your Desktops   http://userful.com/
............................

Re: [coLinux-users] 64bit support

[Jun Li <ol...@gm...>]

I have asked for 64-bit coLinux for years but did not get any progress. I
guess it is time for the dev team to make it higher priority now.


On Mon, Mar 12, 2012 at 6:53 AM, David Kaufman <da...@gi...> wrote:

> Hi Lorne!
>
> The lack of 64-bit support is becoming more and more of a problem for me
> too.  I just bought a new laptop and was finally forced into the 64-bit
> hinterlands of Windows 7 -- can't hardly even *buy* a new laptop with
> less that 4 gigs these days.
>
> So... no coLinux for me? :-(
>
> -dave
>
>
> On 3/5/2012 5:08 PM, Lorne Sturtevant wrote:
> > We're currently using coLinux for a project.  We're using it in 32 bit
> > mode right now, but we require 64bit support.  We noticed there was a
> > posting for someone else wanting this on oDesk back in Novemenber, but
> > nothing seems to have come from that.
> >
> > Is there anyone out there that can add the 64 bit support?  We'll be
> > able to pay anyone that can perform the work.  All the code can be kept
> > under the same license.  We just need 64 bit to work.
> >
>
>
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] 64bit support

[David K. <da...@gi...>]

Hi Lorne!

The lack of 64-bit support is becoming more and more of a problem for me 
too.  I just bought a new laptop and was finally forced into the 64-bit 
hinterlands of Windows 7 -- can't hardly even *buy* a new laptop with 
less that 4 gigs these days.

So... no coLinux for me? :-(

-dave


On 3/5/2012 5:08 PM, Lorne Sturtevant wrote:
> We're currently using coLinux for a project.  We're using it in 32 bit
> mode right now, but we require 64bit support.  We noticed there was a
> posting for someone else wanting this on oDesk back in Novemenber, but
> nothing seems to have come from that.
>
> Is there anyone out there that can add the 64 bit support?  We'll be
> able to pay anyone that can perform the work.  All the code can be kept
> under the same license.  We just need 64 bit to work.
>

[coLinux-users] 64bit support

[Lorne S. <lst...@us...>]

We're currently using coLinux for a project.  We're using it in 32 bit
mode right now, but we require 64bit support.  We noticed there was a
posting for someone else wanting this on oDesk back in Novemenber, but
nothing seems to have come from that.

Is there anyone out there that can add the 64 bit support?  We'll be
able to pay anyone that can perform the work.  All the code can be kept
under the same license.  We just need 64 bit to work.

-- 
Lorne Sturtevant
Senior Programmer
Userful Corporation (GMT -7)
Tel: +1.403-235-5343 | Fax: +1.403-206-7010 | Skype: lorne.sturtevant
Suite 200, 709 11th Ave. SW, Calgary, AB, T2R 0E3 CANADA
Manage & Multiply your Desktops   http://userful.com/
............................

Re: [coLinux-users] coLinux-users Digest, Vol 69, Issue 2

[Alexander K. <kri...@fr...>]

Well, actually I succeeded now with simple examples like one-process,
one-I/O-channel stuff, e.g. a long-running "find /" on one console,
transferring it to another. I could not manage to get a "mc" session to
another TTY though. Maybe this is because of the sub-shell in mc. But I
am also failing at a simple "make menuconfig" because make also has a
sub-process (mconf). I can only transfer "leaves" of a process tree,
i.e. the mconf instance itself.

Do you succeed in doing such stuff?


BTW: Why is the reply-to header wrong in this list and I am always
replaying to people privately in the first try?
--
Alexander Kriegisch (kriegaex)
http://freetz.org


Johann Pascher, 03.02.2012 18:40:
> Hi Alexander Kriegisch (kriegaex),
> 
> I don't have any problem with it on Ubuntu 12.04 (speedlinux)
> Did test with this example:
> http://monkeypatch.me/blog/move-a-running-process-to-a-new-screen-shell.html
> Best regards, Johann Pascher
> 
> 2012/2/3  <col...@li...>:
>> Send coLinux-users mailing list submissions to
>>        col...@li...
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>        https://lists.sourceforge.net/lists/listinfo/colinux-users
>> or, via email, send a message with subject or body 'help' to
>>        col...@li...
>>
>> You can reach the person managing the list at
>>        col...@li...
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of coLinux-users digest..."
>>
>>
>> Today's Topics:
>>
>>   1. Re: Problem with ptrace protection in Ubuntu (yin sun)
>>   2. Re: Problem with ptrace protection in Ubuntu (yin sun)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 2 Feb 2012 18:28:04 -0800
>> From: yin sun <sun...@gm...>
>> Subject: Re: [coLinux-users] Problem with ptrace protection in Ubuntu
>> To: col...@li...
>> Message-ID:
>>        <CAKPZSeDNDgjSUHZEcJDpYQ-WwYBcZV8YZZ=Vzk...@ma...>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> I guess you are right, there is no yama LSM in 2.6.33.7
>>
>> /Yin
>>
>> On Tue, Jan 31, 2012 at 8:48 PM, Alexander Kriegisch
>> <kri...@fr...> wrote:
>>> Hi.
>>>
>>> I am running andLinux/coLinux:
>>>
>>> $ uname -a
>>> Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux
>>>
>>> But...
>>>
>>> $ cat /etc/motd | head -n 1
>>> Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)
>>>
>>> Now the problem is so-called "ptrace protection", explained there:
>>> https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection
>>>
>>> I tried to use tools like reptyr and injcode:
>>> https://github.com/nelhage/reptyr#readme
>>> https://github.com/ThomasHabets/injcode#readme
>>>
>>> Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel (without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.
>>>
>>> My questions are:
>>> ?1) Can you confirm that my suscpcion is correct?
>>> ? ?2a) If not, what else might be the reason for my problems?
>>> ? ?2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support from somewhere or asking you to build in yama protection in the future?
>>>
>>> Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.
>>>
>>> Any help is appreciated. Thanks in advance.
>>> --
>>> Alexander Kriegisch (kriegaex)
>>> http://freetz.org
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Keep Your Developer Skills Current with LearnDevNow!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-d2d
>>> _______________________________________________
>>> coLinux-users mailing list
>>> coL...@li...
>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 2 Feb 2012 21:47:25 -0800
>> From: yin sun <sun...@gm...>
>> Subject: Re: [coLinux-users] Problem with ptrace protection in Ubuntu
>> To: col...@li...
>> Message-ID:
>>        <CAK...@ma...>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> OK, I tried on my debian 6.0.3 (latest colinux kernel), rettyer works.
>> And I am sure the colinux doesn't have yama. whether have yama or not
>> may not be your problem.
>> Since it only provide protection for non root user.
>> not sure what else could be wrong, sorry can't help you more.
>>
>> /Yin
>>
>>
>>
>> On Thu, Feb 2, 2012 at 6:28 PM, yin sun <sun...@gm...> wrote:
>>> I guess you are right, there is no yama LSM in 2.6.33.7
>>>
>>> /Yin
>>>
>>> On Tue, Jan 31, 2012 at 8:48 PM, Alexander Kriegisch
>>> <kri...@fr...> wrote:
>>>> Hi.
>>>>
>>>> I am running andLinux/coLinux:
>>>>
>>>> $ uname -a
>>>> Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux
>>>>
>>>> But...
>>>>
>>>> $ cat /etc/motd | head -n 1
>>>> Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)
>>>>
>>>> Now the problem is so-called "ptrace protection", explained there:
>>>> https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection
>>>>
>>>> I tried to use tools like reptyr and injcode:
>>>> https://github.com/nelhage/reptyr#readme
>>>> https://github.com/ThomasHabets/injcode#readme
>>>>
>>>> Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel (without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.
>>>>
>>>> My questions are:
>>>> ?1) Can you confirm that my suscpcion is correct?
>>>> ? ?2a) If not, what else might be the reason for my problems?
>>>> ? ?2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support from somewhere or asking you to build in yama protection in the future?
>>>>
>>>> Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.
>>>>
>>>> Any help is appreciated. Thanks in advance.
>>>> --
>>>> Alexander Kriegisch (kriegaex)
>>>> http://freetz.org
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Keep Your Developer Skills Current with LearnDevNow!
>>>> The most comprehensive online learning library for Microsoft developers
>>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>>> http://p.sf.net/sfu/learndevnow-d2d
>>>> _______________________________________________
>>>> coLinux-users mailing list
>>>> coL...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>>
>>
>> ------------------------------
>>
>> ------------------------------------------------------------------------------
>> Try before you buy = See our experts in action!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-dev2
>>
>> ------------------------------
>>
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>>
>> End of coLinux-users Digest, Vol 69, Issue 2
>> ********************************************
> 
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 

Re: [coLinux-users] coLinux-users Digest, Vol 69, Issue 2

[Johann P. <joh...@gm...>]

Hi Alexander Kriegisch (kriegaex),

I don't have any problem with it on Ubuntu 12.04 (speedlinux)
Did test with this example:
http://monkeypatch.me/blog/move-a-running-process-to-a-new-screen-shell.html
Best regards, Johann Pascher

2012/2/3  <col...@li...>:
> Send coLinux-users mailing list submissions to
>        col...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/colinux-users
> or, via email, send a message with subject or body 'help' to
>        col...@li...
>
> You can reach the person managing the list at
>        col...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of coLinux-users digest..."
>
>
> Today's Topics:
>
>   1. Re: Problem with ptrace protection in Ubuntu (yin sun)
>   2. Re: Problem with ptrace protection in Ubuntu (yin sun)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 2 Feb 2012 18:28:04 -0800
> From: yin sun <sun...@gm...>
> Subject: Re: [coLinux-users] Problem with ptrace protection in Ubuntu
> To: col...@li...
> Message-ID:
>        <CAKPZSeDNDgjSUHZEcJDpYQ-WwYBcZV8YZZ=Vzk...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I guess you are right, there is no yama LSM in 2.6.33.7
>
> /Yin
>
> On Tue, Jan 31, 2012 at 8:48 PM, Alexander Kriegisch
> <kri...@fr...> wrote:
>> Hi.
>>
>> I am running andLinux/coLinux:
>>
>> $ uname -a
>> Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux
>>
>> But...
>>
>> $ cat /etc/motd | head -n 1
>> Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)
>>
>> Now the problem is so-called "ptrace protection", explained there:
>> https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection
>>
>> I tried to use tools like reptyr and injcode:
>> https://github.com/nelhage/reptyr#readme
>> https://github.com/ThomasHabets/injcode#readme
>>
>> Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel (without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.
>>
>> My questions are:
>> ?1) Can you confirm that my suscpcion is correct?
>> ? ?2a) If not, what else might be the reason for my problems?
>> ? ?2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support from somewhere or asking you to build in yama protection in the future?
>>
>> Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.
>>
>> Any help is appreciated. Thanks in advance.
>> --
>> Alexander Kriegisch (kriegaex)
>> http://freetz.org
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 2 Feb 2012 21:47:25 -0800
> From: yin sun <sun...@gm...>
> Subject: Re: [coLinux-users] Problem with ptrace protection in Ubuntu
> To: col...@li...
> Message-ID:
>        <CAK...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> OK, I tried on my debian 6.0.3 (latest colinux kernel), rettyer works.
> And I am sure the colinux doesn't have yama. whether have yama or not
> may not be your problem.
> Since it only provide protection for non root user.
> not sure what else could be wrong, sorry can't help you more.
>
> /Yin
>
>
>
> On Thu, Feb 2, 2012 at 6:28 PM, yin sun <sun...@gm...> wrote:
>> I guess you are right, there is no yama LSM in 2.6.33.7
>>
>> /Yin
>>
>> On Tue, Jan 31, 2012 at 8:48 PM, Alexander Kriegisch
>> <kri...@fr...> wrote:
>>> Hi.
>>>
>>> I am running andLinux/coLinux:
>>>
>>> $ uname -a
>>> Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux
>>>
>>> But...
>>>
>>> $ cat /etc/motd | head -n 1
>>> Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)
>>>
>>> Now the problem is so-called "ptrace protection", explained there:
>>> https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection
>>>
>>> I tried to use tools like reptyr and injcode:
>>> https://github.com/nelhage/reptyr#readme
>>> https://github.com/ThomasHabets/injcode#readme
>>>
>>> Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel (without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.
>>>
>>> My questions are:
>>> ?1) Can you confirm that my suscpcion is correct?
>>> ? ?2a) If not, what else might be the reason for my problems?
>>> ? ?2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support from somewhere or asking you to build in yama protection in the future?
>>>
>>> Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.
>>>
>>> Any help is appreciated. Thanks in advance.
>>> --
>>> Alexander Kriegisch (kriegaex)
>>> http://freetz.org
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Keep Your Developer Skills Current with LearnDevNow!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-d2d
>>> _______________________________________________
>>> coLinux-users mailing list
>>> coL...@li...
>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
>
> ------------------------------
>
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>
> End of coLinux-users Digest, Vol 69, Issue 2
> ********************************************

Re: [coLinux-users] Problem with ptrace protection in Ubuntu

[Alexander K. <kri...@fr...>]

Thanks Yin for testing this and trying to help me.

Probably you mean either reptyr or retty when you mention that you
tested this on your system (I do not know a tool named rettyer).

I do not know about Debian 6.0.3, but I guess it does not have yama in
its original kernel so there is no damage done if colinux does not have
it either. Debian 6.0.3 just does not expect it. so the test is kind of
pointless. Let me explain (again) why: I am running Ubuntu 11.10. Its
original kernel *does* have yama, so the rest of the system expects it
to exist. Probably it checks the return value of
/proc/sys/kernel/yama/ptrace_scope, but that "file" does not exist if
there is no yama. Now reptyr even knows about yama, showing a warning
message if /proc/sys/kernel/yama/ptrace_scope returns 1. As soon as I
set it to 0 on my native Ubuntu, reptyr works nicely. I guess it also
does on colinux if you use an OS which does not expect yama ptrace
protection to be in the kernel, e.g. an older Ubuntu or probably your
Debian 6.0.3.

Do you understand the issue at hand now? I hope I made myself clearer
now. Maybe you have a clue for me. Is there a way to simulate this
"file" /proc/sys/kernel/yama/ptrace_scope and make it always return 0 so
Ubuntu and reptyr are satisfied?

Thanks again
--
Alexander


yin sun, 03.02.2012 06:47:
> OK, I tried on my debian 6.0.3 (latest colinux kernel), rettyer works.
> And I am sure the colinux doesn't have yama. whether have yama or not
> may not be your problem.
> Since it only provide protection for non root user.
> not sure what else could be wrong, sorry can't help you more.
> 
> /Yin
> 
> 
> 
> On Thu, Feb 2, 2012 at 6:28 PM, yin sun <sun...@gm...> wrote:
>> I guess you are right, there is no yama LSM in 2.6.33.7
>>
>> /Yin
>>
>> On Tue, Jan 31, 2012 at 8:48 PM, Alexander Kriegisch
>> <kri...@fr...> wrote:
>>> Hi.
>>>
>>> I am running andLinux/coLinux:
>>>
>>> $ uname -a
>>> Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux
>>>
>>> But...
>>>
>>> $ cat /etc/motd | head -n 1
>>> Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)
>>>
>>> Now the problem is so-called "ptrace protection", explained there:
>>> https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection
>>>
>>> I tried to use tools like reptyr and injcode:
>>> https://github.com/nelhage/reptyr#readme
>>> https://github.com/ThomasHabets/injcode#readme
>>>
>>> Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel (without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.
>>>
>>> My questions are:
>>>  1) Can you confirm that my suscpcion is correct?
>>>    2a) If not, what else might be the reason for my problems?
>>>    2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support from somewhere or asking you to build in yama protection in the future?
>>>
>>> Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.
>>>
>>> Any help is appreciated. Thanks in advance.

Re: [coLinux-users] Problem with ptrace protection in Ubuntu

[yin s. <sun...@gm...>]

OK, I tried on my debian 6.0.3 (latest colinux kernel), rettyer works.
And I am sure the colinux doesn't have yama. whether have yama or not
may not be your problem.
Since it only provide protection for non root user.
not sure what else could be wrong, sorry can't help you more.

/Yin



On Thu, Feb 2, 2012 at 6:28 PM, yin sun <sun...@gm...> wrote:
> I guess you are right, there is no yama LSM in 2.6.33.7
>
> /Yin
>
> On Tue, Jan 31, 2012 at 8:48 PM, Alexander Kriegisch
> <kri...@fr...> wrote:
>> Hi.
>>
>> I am running andLinux/coLinux:
>>
>> $ uname -a
>> Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux
>>
>> But...
>>
>> $ cat /etc/motd | head -n 1
>> Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)
>>
>> Now the problem is so-called "ptrace protection", explained there:
>> https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection
>>
>> I tried to use tools like reptyr and injcode:
>> https://github.com/nelhage/reptyr#readme
>> https://github.com/ThomasHabets/injcode#readme
>>
>> Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel (without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.
>>
>> My questions are:
>>  1) Can you confirm that my suscpcion is correct?
>>    2a) If not, what else might be the reason for my problems?
>>    2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support from somewhere or asking you to build in yama protection in the future?
>>
>> Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.
>>
>> Any help is appreciated. Thanks in advance.
>> --
>> Alexander Kriegisch (kriegaex)
>> http://freetz.org
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Problem with ptrace protection in Ubuntu

[yin s. <sun...@gm...>]

I guess you are right, there is no yama LSM in 2.6.33.7

/Yin

On Tue, Jan 31, 2012 at 8:48 PM, Alexander Kriegisch
<kri...@fr...> wrote:
> Hi.
>
> I am running andLinux/coLinux:
>
> $ uname -a
> Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux
>
> But...
>
> $ cat /etc/motd | head -n 1
> Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)
>
> Now the problem is so-called "ptrace protection", explained there:
> https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection
>
> I tried to use tools like reptyr and injcode:
> https://github.com/nelhage/reptyr#readme
> https://github.com/ThomasHabets/injcode#readme
>
> Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel (without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.
>
> My questions are:
>  1) Can you confirm that my suscpcion is correct?
>    2a) If not, what else might be the reason for my problems?
>    2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support from somewhere or asking you to build in yama protection in the future?
>
> Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.
>
> Any help is appreciated. Thanks in advance.
> --
> Alexander Kriegisch (kriegaex)
> http://freetz.org
>
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] Problem with ptrace protection in Ubuntu

[Alexander K. <kri...@fr...>]

Hi.

I am running andLinux/coLinux:

$ uname -a
Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux

But...

$ cat /etc/motd | head -n 1
Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)

Now the problem is so-called "ptrace protection", explained there:
https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection

I tried to use tools like reptyr and injcode:
https://github.com/nelhage/reptyr#readme
https://github.com/ThomasHabets/injcode#readme

Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel (without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.

My questions are:
  1) Can you confirm that my suscpcion is correct?
    2a) If not, what else might be the reason for my problems?
    2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support from somewhere or asking you to build in yama protection in the future?

Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.

Any help is appreciated. Thanks in advance.
--
Alexander Kriegisch (kriegaex)
http://freetz.org

Re: [coLinux-users] Colinux Blue Screen Crashes

[mawcowboy <vw...@bi...>]

Hi Bob,
Just another idea.  
My Computer --> System Properties --> Advanced --> Startup and Recovery -
Settings --> Write debugging information --> Small memory dump
then download 
http://www.nirsoft.net/utils/blue_screen_view.html
What drivers does this utility indicate is at fault?
Regards,
Mark

-----


Hi Bob,
Not sure what to do here for you.  I feel I should point out that I googled
3,000 hits with the search string "nt!KiFastCallEntry+0xf8 nt!KiTrap0E+0x233
", This seems most likely a windows driver problem.
If I add "colinux" to my search only your messages are found.  I would
continue investigation with the likely causes of "nt!KiFastCallEntry+0xf8
nt!KiTrap0E+0x233". 
Here is a tool that will show you what drivers are active on your system, 
http://www.nirsoft.net/utils/driverview.html
This information may help.
Regards, 
Mark Washburn

------------

-- 
View this message in context: http://old.nabble.com/Colinux-blue-screen-crashes-tp33076511p33191688.html
Sent from the colinux-users mailing list archive at Nabble.com.

Re: [coLinux-users] Colinux blue screen crashes

[Henry N. <hen...@ar...>]

Exactly, that is the problem. In the logs we only can the the coruppted
memory, but not the task who changed it.

For the test:
I have started a minimal Debian 4 with 128 MB RAM and no swapfile and in
there I started this Script:

=== start memeater.sh ===
#!/bin/sh

eat()
{
    sleep 100
}

count=0
while [ $count -le 10000 ]
do
    count=$(( $count + 1 ))
    eat &
done                                                                                                                                                        

===end memeater.sh ===

Warning! This Script starts lot of sub shells. For my my system, it was
unstable near 700 running tasks. I saw kernel messages "oom-killer ...
sh killed" inside coLinux console. But no problems on Windows side. I
have a Single Core 2.1GHz Windows XP.
Run the "sync.exe" from
http://technet.microsoft.com/en-en/sysinternals/bb897438 to save your
unbuffered files, before you forces the blue screen.

An other simple memory test you can do with the default initrd.gz from
coLinux installation.
Save the script as file "memeater.sh" into your coLinux install path
(for example "c:\colinux")

Run coLinux:

    sync.exe
    cd c:\colinux
    colinux-daemon kernel=vmlinux mem=128 initrd=initrd.gz
root=/dev/ram0 cofs0=.

Inside Linux ramdisk run theses commands:

    mount -t cofs cofs0 /mnt
    sh
    cd /mnt
    sh ./memeater.sh

For me here is the same effect: coLinux kernel kills unused task "sleep
100" via oom-killer, and Windows runs very stable.
If you have more RAM for coLinux in use, the increase the total count of
task inside the script.

I remember for a very old bug inside some Intel CPUs from the Core 2
Duo. There was an internal problem with the CPU cache lines, because
coLinux switches to fast the complete Page-Tables without flush. Maybe
your CPU has similar (but other, because the oldy has a workaround) and
you can disable the CPU-Cache in your BIOS for a test cycle.

What is your exactly CPU type. Please use a tool from manufacture. Then
we can locate an existing errata for this.

-- 
Henry N.

Re: [coLinux-users] Colinux blue screen crashes

[yin s. <sun...@gm...>]

I remember someone suggest to try another distribution, disable
certain features etc, to narrow down the scope. Maybe you can
summarize what have been tried, and try to analyze the dump yourselves
to give us some directions.
There is really no sure way as a productive path when processes stump
on each other.
Please try as much as you can.


Thanks,

On Tue, Jan 24, 2012 at 11:38 AM, Bob Wheater <bwh...@my...> wrote:
> Qnx4ever wrote:
>
>> but I'm a bit annoyed by the tone of your messages.
>
> You are easily annoyed. Maybe your skin is too thin.
>
> I see no reason for you to be annoyed. You are not on
>
> The list of colinux developers. So what is your relation
>
> To the colinux project if any? If you don’t work for colinux project then
> your comments should be ignored.
>
>
>
>>Maybe there's something wrong with your PC if no one >else had similar
>> issues ?
>
> This PC had no blue screen crashes for 5+ years of running Windows XP. The
> crashes only occurred when I started running colinux and they don’t occur on
> the days
>
> That I don’t run colinux. Since many users may not frequently use up 95% or
> greater of memory they may not encounter this problem.
>
>
>
>>Does anyone care about this new Ubuntu release,
>
> Maybe the thousands of downloaders of Portable Ubuntu do care.
>
>
>
>>piss everyone off ?
>
> I doubt if you speak for everyone.  Your comments are no  help to anyone.
>
>
>
>>>These things that you have asked me to try seem like a >>waste of time so
>>> far.
>
>>>It would be better if somebody that understands >>colinux well looked at
>>> the patterns in memory where >>the corruption is detected to see if they
>>> recognize >>anything related to what colinux is doing.
>
> The operative word here is “seem”.  Here I am suggesting  a more productive
> path than the trial and error method that was suggested. I have spent 2
> months so far with Kaspersky and Colinux trying to solve this problem.
> Kaspersky has determined that it is not caused by them. The tests with ndis,
> pcap, slirp indicate that it does not matter which networking mode is being
> used as the crash occurs on all modes. Obvious, I find this frustrating that
> it is taking so long to get this problem solved.
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] Colinux blue screen crashes

[Bob W. <bwh...@my...>]

Qnx4ever wrote:

> but I'm a bit annoyed by the tone of your messages.

You are easily annoyed. Maybe your skin is too thin.

I see no reason for you to be annoyed. You are not on

The list of colinux developers. So what is your relation

To the colinux project if any? If you don't work for colinux project then
your comments should be ignored.

 

>Maybe there's something wrong with your PC if no one >else had similar
issues ? 

This PC had no blue screen crashes for 5+ years of running Windows XP. The
crashes only occurred when I started running colinux and they don't occur on
the days

That I don't run colinux. Since many users may not frequently use up 95% or
greater of memory they may not encounter this problem.

 

>Does anyone care about this new Ubuntu release,

Maybe the thousands of downloaders of Portable Ubuntu do care.

 

>piss everyone off ? 

I doubt if you speak for everyone.  Your comments are no  help to anyone.

 

>>These things that you have asked me to try seem like a >>waste of time so
far.

>>It would be better if somebody that understands >>colinux well looked at
the patterns in memory where >>the corruption is detected to see if they
recognize >>anything related to what colinux is doing.

The operative word here is "seem".  Here I am suggesting  a more productive
path than the trial and error method that was suggested. I have spent 2
months so far with Kaspersky and Colinux trying to solve this problem.
Kaspersky has determined that it is not caused by them. The tests with ndis,
pcap, slirp indicate that it does not matter which networking mode is being
used as the crash occurs on all modes. Obvious, I find this frustrating that
it is taking so long to get this problem solved.

[coLinux-users] Your Ubuntu bluescreens !

[qnx4ever <qnx...@gm...>]

Hello Bob,
Not sure about Henry, but I'm a bit annoyed by the tone of your
messages. Maybe you should try harder to figure out issue yourself ?
Maybe there's something wrong with your PC if no one else had similar
issues ? Does anyone care about this new Ubuntu release, you piss
everyone off ? Pardon my French ;) Nothing personal...

>These things that you have asked me to try seem like a waste of time so far.
It would be better if somebody that understands colinux well looked at the
patterns in memory where the corruption is detected to see if they recognize
anything related to what colinux is doing.