Why this “=> /lib64/libpthread.so.0 ” instantly crashes the kernel

sluge · 12-26-2018, 01:06 AM

I executed under root:

Code:

 => /lib64/libpthread.so.0

And it crashes my kernel on RHEL 7.3. Why? Just to redirection to the lib? After reboot Linux works Ok

PS: On Ubuntu I got "permission denied" even on sudo

pan64 · 12-26-2018, 04:54 AM

I would say we have no idea what's going on. http://catb.org/~esr/faqs/smart-ques...html#beprecise

berndbausch · 12-26-2018, 05:23 AM

I get

Code:

# => /lib64/libpthread.so.0
-bash: =: command not found

after which the ssh connection breaks, which doesn’t surprise me after wrecking an essential shared library.

But I can still ping the server. No panic.

Admittedly, this is CentOS Linux release 7.4.1708, not 7.3.

pan64 · 12-26-2018, 05:39 AM

if that redirection was successful you would destroy your lib and you cannot even properly reboot next time.
bash will open that file before checking the command itself - based on some test (on ubuntu) the file was created (and also first destroyed). But it definitely does not crash the kernel, just your GUI. And will not be recovered automatically at the next boot.

sluge · 12-27-2018, 01:14 AM

Quote:

Originally Posted by berndbausch

I get

Code:

# => /lib64/libpthread.so.0
-bash: =: command not found

For CentOs 6 it crashes for me

berndbausch · 12-27-2018, 02:31 AM

Quote:

Originally Posted by sluge

For CentOs 6 it crashes for me

And you are right.

Sorry for my more than misleading post; I was pinging the server when it was already rebooting. But reboot it did. Centos 7. Mysterious.

This is a VM that I ssh'd into. I have not taken the time to try this on the console.

pan64 · 12-28-2018, 03:05 AM

what do you mean by crash?
But anyway, if system was crashed, probably the destroyed file could not be saved on the disk, that's why it worked next time.

sluge · 12-29-2018, 12:25 AM

Quote:

Originally Posted by pan64

what do you mean by crash?

Linux kernel crash this is the system crash

pan64 · 12-29-2018, 05:18 AM

how do you know if that was the linux kernel?