search for: kmem

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:06.kmem Security Advisory The FreeBSD Project Topic: Local kernel memory disclosure Category: core Module: kernel Announced: 2006-01-25 Credits: Xin LI, Karl Janmar Affects:...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:06.kmem Security Advisory The FreeBSD Project Topic: Local kernel memory disclosure Category: core Module: kernel Announced: 2006-01-25 Credits: Xin LI, Karl Janmar Affects:...

Suddenly i found an error while booting, it says: Fuck: can't open /dev/kmem for read/write (2) So this is why, the Asterisk and Zaptel can not start. Any Suggestions Please Thanks a lot Torintino _________________________________________________________________ Windows Live: Make it easier for your friends to see what you?re up to on Facebook. http://www....

...0.02u 0.04s 0% 3404k Worked for a while then that stopped working too (was over ssh). When trying a local login i only got load: 0.09 cmd: login 1611 [zfs] 0.00u 0.00s 0% 208k I found one post like this earlier (by Xin LI), but nobody seemed to have replied... in my current conf, I think my kmem/kmem_max is at 512Mb (not sure though, since I've edited my file yesterday for next reboot), with 2G of system RAM.. Normally I'd run kmem(max) 1G (with arcsize of 512M. currently it is at default), but since I just got back to 2G total mem after some hardware problems I've been...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:25.kmem Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in firewire(4) Category: core Module: sys_dev Announced: 2006-12-06 Credits: Rodrigo Rubira Bran...

...roup.clone_children --w--w--w- 1 root root 0 Sep 15 17:14 cgroup.event_control -rw-r--r-- 1 root root 0 Sep 15 17:15 cgroup.procs -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.failcnt --w------- 1 root root 0 Sep 15 17:14 memory.force_empty -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.kmem.failcnt -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.kmem.limit_in_bytes -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.kmem.max_usage_in_bytes -r--r--r-- 1 root root 0 Sep 15 17:14 memory.kmem.slabinfo -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.kmem.tcp.failcnt -rw-r--r-- 1 root root...

... or buddy userspace. patching `sys_vmsplice()' with `ret'. 1)# echo -e '\xc3' | dd of=/dev/kmem bs=1 count=1 seek=$((0x`cat /proc/kallsyms|grep sys_vmsplice | awk {'print $1'}`)) 2)# echo -e '\xc3' | dd of=/dev/kmem bs=1 count=1 seek=$((0x`awk '/sys_vmsplice/ { print $1; }' /proc/kallsyms`)) my try: # # printf "\xC3" | dd bs=1 count=1 of=/dev/km...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-05:08.kmem Security Advisory The FreeBSD Project Topic: Local kernel memory disclosure Category: core Module: sys Announced: 2005-05-06 Credits: Christian S.J. Peron Affects:...

This is the follow up of [1]: [PATCH v1 0/3] mm/memory_hotplug: Make virtio-mem play nicely with kexec-tools I realized that this is not only helpful for virtio-mem, but also for dax/kmem - it's a fix for that use case (see patch #3) of persistent memory. Also, while testing, I discovered that kexec-tools will *not* add dax/kmem memory (anything not directly under the root when parsing /proc/iomem) to the elfcorehdr, so this memory will never get included in a dump. This probab...

...namespace0.0 3280000000-32ffffffff : PCI Bus 0000:00 After configuring the namespace: [root at localhost ~]# cat /proc/iomem ... 140000000-33fffffff : Persistent Memory 140000000-1481fffff : namespace0.0 148200000-33fffffff : dax0.0 3280000000-32ffffffff : PCI Bus 0000:00 After loading kmem: [root at localhost ~]# cat /proc/iomem ... 140000000-33fffffff : Persistent Memory 140000000-1481fffff : namespace0.0 150000000-33fffffff : dax0.0 150000000-33fffffff : System RAM 3280000000-32ffffffff : PCI Bus 0000:00 After a proper reboot: [root at localhost ~]# cat /proc/iomem...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-05:08.kmem Security Advisory The FreeBSD Project Topic: Local kernel memory disclosure Category: core Module: sys Announced: 2005-05-06 Credits: Christian S.J. Peron...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-05:08.kmem Security Advisory The FreeBSD Project Topic: Local kernel memory disclosure Category: core Module: sys Announced: 2005-05-06 Credits: Christian S.J. Peron...

...ded via HyperV balloon (unless memory is unplugged via > >> ballooning and you reboot ... the the e820 is changed as well). I assume > >> we wanted to be able to reflect that, to make kexec look like a real reboot. > >> > >> This worked for a while. Then came dax/kmem. Now comes virtio-mem. > >> > >> > >> But I assume only Andrew can enlighten us. > >> > >> @Andrew, any guidance here? Should we really add all memory to the > >> firmware memmap, even if this contradicts with the existing > >> document...

...ded via HyperV balloon (unless memory is unplugged via > >> ballooning and you reboot ... the the e820 is changed as well). I assume > >> we wanted to be able to reflect that, to make kexec look like a real reboot. > >> > >> This worked for a while. Then came dax/kmem. Now comes virtio-mem. > >> > >> > >> But I assume only Andrew can enlighten us. > >> > >> @Andrew, any guidance here? Should we really add all memory to the > >> firmware memmap, even if this contradicts with the existing > >> document...

...gt;>>>>> ballooning and you reboot ... the the e820 is changed as well). I assume >>>>>>> we wanted to be able to reflect that, to make kexec look like a real reboot. >>>>>>> >>>>>>> This worked for a while. Then came dax/kmem. Now comes virtio-mem. >>>>>>> >>>>>>> >>>>>>> But I assume only Andrew can enlighten us. >>>>>>> >>>>>>> @Andrew, any guidance here? Should we really add all memory to the >>>>>&...

...gt;>>>>> ballooning and you reboot ... the the e820 is changed as well). I assume >>>>>>> we wanted to be able to reflect that, to make kexec look like a real reboot. >>>>>>> >>>>>>> This worked for a while. Then came dax/kmem. Now comes virtio-mem. >>>>>>> >>>>>>> >>>>>>> But I assume only Andrew can enlighten us. >>>>>>> >>>>>>> @Andrew, any guidance here? Should we really add all memory to the >>>>>&...

...anged as well). I assume >>>>>>>>>>>>> we wanted to be able to reflect that, to make kexec look like a real reboot. >>>>>>>>>>>>> >>>>>>>>>>>>> This worked for a while. Then came dax/kmem. Now comes virtio-mem. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> But I assume only Andrew can enlighten us. >>>>>>>>>>>>> >>>>>&...

...anged as well). I assume >>>>>>>>>>>>> we wanted to be able to reflect that, to make kexec look like a real reboot. >>>>>>>>>>>>> >>>>>>>>>>>>> This worked for a while. Then came dax/kmem. Now comes virtio-mem. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> But I assume only Andrew can enlighten us. >>>>>>>>>>>>> >>>>>&...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-05:08.kmem Security Advisory The FreeBSD Project Topic: Local kernel memory disclosure Category: core Module: sys Announced: 2005-05-06 Credits: Christian S.J. Peron Affects:...

...on comp.unix.bsd.freebsd.misc but i was advised to send here I was unable to find help on google :( To resume quick, when i'm in a jail, netstat doesn't work properly. Hopefully i have provided sufficient information for anyone willing to help me :p First of all, my system : FreeBSD cube.kmem.org 4.8-STABLE FreeBSD 4.8-STABLE #6: Tue May 20 22:22:47 CEST 2003 root@cube.kmem.org:/usr/obj/usr/src/sys/ruby2 i386 System was updated, mergemaster done, kernel in sync with world. The interfaces par of my rc.conf from the host : ifconfig_rl1="inet 10.0.2.1 netmask 255.255.255.0&qu...