similar to: klibc loader crash...

On Thu, Feb 06, 2020 at 04:38:34PM +0100, Christophe Leroy wrote: > With latest kernel (Linus tree as of 5.6 merge window), I get the following > warning in the kernel 'dmesg': > > [ 5.746588] process '/bin/sh' started with executable stack > > This comes from commit

With latest kernel (Linus tree as of 5.6 merge window), I get the following warning in the kernel 'dmesg': [ 5.746588] process '/bin/sh' started with executable stack This comes from commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/exec.c?id=47a2ebb7f5053387f5753b524f4920b9b829f922 "execve: warn if process starts with executable

Here's a small test program to find out where a klibc executable expects its shared library (or interpreter to be precise) to be. It should work regardless of 32/64 bit, little- or big-endian, but only on native executables. If you have access to a 64-bit or big endian machine, I would appreciate feedback on whether it produces correct answers on your machine. To run the test, cut the

Folks -- I''m trying to run FreeBSD 6.0 on a VT-x based Xen system. I''m experiencing a problem where the boot loader is crashing before the FreeBSD kernel (proper) is loaded. The sequence of operations is that the VMX domain is constructed, the BIOS is executed, GRUB loads, I type the instructions to load FreeBSD (a boot loader) and that code begins to execute and then

hello guys. i've been digging through the mail list archive for a few days, to no avail. i hope you can help me : i want to create a bootable DOS image, approximately 25MB , to boot a system from the network, using PXELINUX . now, i've followed some instructions on this list, but the image always fails to boot. the only thing which succeeds, is to take a bootable DOS disk, put it in

If you compiled your kernel and booted under Xen and got: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x9db000 (XEN) elf_parse_binary: phdr: paddr=0x1a00000 memsz=0xa30f0 (XEN) elf_parse_binary: phdr: paddr=0x1aa4000 memsz=0x13c00 (XEN) elf_parse_binary: phdr: paddr=0x1ab8000 memsz=0x206000 (XEN) elf_parse_binary: memory: 0x1000000 -> 0x1cbe000 (XEN)

So I'm exploring AUDIT and have this in /etc/security/audit_control: dir:/var/audit flags:lo,fd minfree:20 naflags:lo policy:cnt filesz:0 I tell auditd to reread the config file with audit -s but no file deletion events are logged. I change the config file to: dir:/var/audit flags:lo minfree:20 naflags:lo,fd policy:cnt filesz:0 I type audit -s and am immediately flooded with 20 kilobytes

So I'm exploring AUDIT and have this in /etc/security/audit_control: dir:/var/audit flags:lo,fd minfree:20 naflags:lo policy:cnt filesz:0 I tell auditd to reread the config file with audit -s but no file deletion events are logged. I change the config file to: dir:/var/audit flags:lo minfree:20 naflags:lo,fd policy:cnt filesz:0 I type audit -s and am immediately flooded with 20 kilobytes

Hi all I keep on getting this error when I try and install a Xen guest on a CentOS 5.1 x64 server with Xen installed from the repositories: [root at gimbli ~]# virt-install sdl=0 vnc=0 nographic=0 -v --location=http://intranet/kickstart/cPanel/centos/5.1/32/os/i386/ --ram=256 --file-size=10 --file=/home/vm/vps07.img --name=vps07 libvir: error : configuration file syntax error: expecting an

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Hi, I set the severity to important as it seems that current xen tools does not allow to load amd64 Debian kernel in DomU. I also put the debian-kernel ML in CC as I'm not sure the problem comes from xen tools or the kernel itself. Here is my configuration: Hypervisor: xen-hypervisor-3.2-1-amd64 3.2.1-2

PE headers code_sz and image_sz indicate more or less, the size of the file and the size of the in-memory image. They are now given the right value. In the ELF format, only the program headers are reliable to determine the actually needed part of the file and the in-memory size. The .bss section should always be marked as NOLOAD for ld since its content shouldn't be included into the binary

PE headers code_sz and image_sz indicate more or less, the size of the file and the size of the in-memory image. They are now given the right value. In the ELF format, only the program headers are reliable to determine the actually needed part of the file and the in-memory size. The .bss section should always be marked as NOLOAD for ld since its content shouldn't be included into the binary

Hi Dave, I remember I read your post, but when I read it, nobody had answered you yet. Thank you very much for the script, it seems to be more complete than mine. I am new to php, to create a script, I usually edit it in notepad and save it as *.php. How can I compile the script '--with-sockets' under windows? Thanks again MAX ________________________________________ From:

Hi all, All of a sudden my xend is crashing, when i do "xm create domu" due to which the domains are created in paused state. Iam using minios as domU kernel, but the problem occurs even for linux-2.6.18.1 pv kernel as domu kernel. xend.log shows [2008-07-31 03:00:54 14821] CRITICAL (SrvDaemon:231) Xend died due to signal 11! Restarting it.... after doing some preliminary

Hi, I have a problematic CentOS XEN server and hope someone could point me in the right direction to optimize it a bit. The server runs on a Core2Quad 9300, with 8GB RAM (max motherboard can take, 1U chassis) on an Intel motherboard with a 1TB SATA HDD. dom0 is set to 512MB limit with a few small XEM VM's running: root at zaxen01:[~]$ xm list Name ID

Hi I''m putting together a Dom0 and three DomU (all Gentoo) with kernel 3.5.7 and Xen 4.1.1. Each Dom has it''s own md (md0 for Dom0, md1 for Dom1 etc). Dom0 works fine so far, however, I''m stuck trying to create DomUs. It appears the xvda1 device on DomU is not created or accessible: Parsing config file dom1 domainbuilder: detail: xc_dom_allocate:

-----BEGIN PGP SIGNED MESSAGE----- ============================================================================= FreeBSD-SA-00:41 Security Advisory FreeBSD, Inc. Topic: Malformed ELF images can cause a system hang Category: core Module: kernel Announced:

Hey, It looks like one of the patches that went in Xen 4.1 blows up. This used to work over the weekend, so I can only surmise it is one the three patches. This is with a debug=y build (which has been working nicely for the last month or more). It looks like one of the patches that went in Xen 4.1 blows up. This used to work a day ago - that is c/s 23551 worked nicely. ----- Forwarded message

Hi, I''m trying to boot a PV VM I just installed (following http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer) without success. My XEN installation is xen-unstable 54c8c9eaee92+ on a Debian unstable machine (x86_64), kernel 3.3.4+. The VM I installed is, again, a Debian unstable x86_64. The installation went smoothly; I used an 8GB file as a disk back-end. I went

Here is some code i wrote to send a mp3 file to a shoutcast server, with a little modification im sure you could change it and use it to connect to icecast2 and write various things etc... not sure but here it is ------------------------------------------------------ <?php $port = '8000'; $ip = '127.0.0.1'; $fileplay = './whatever.mp3'; $password = 'changme'