FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F7.2.0_cvs 2009-05-01T02:51:58Z 2009-05-01T02:51:58Z Ken Smith kensmith@FreeBSD.org 2009-05-01T02:51:58Z urn:sha1:b205d83df7763ca1f099bce5ac12a05862a626c4 Approved by: re (implicit) This commit was manufactured to restore the state of the 7.2-RELEASE image. 2009-04-17T17:05:31Z Dmitry Chagin dchagin@FreeBSD.org 2009-04-17T17:05:31Z urn:sha1:fec900bd043c9dd3300b648b701b1de79a99900d Fix KBI breakage by r190520 which affects older linux.ko binaries: 1) Move the new field (brand_note) to the end of the Brandinfo structure. 2) Add a new flag BI_BRAND_NOTE that indicates that the brand_note pointer is valid. 3) Use the brand_note field if the flag BI_BRAND_NOTE is set and as old modules won't have the flag set, so the new field brand_note would be ignored. Suggested by: jhb Reviewed by: jhb Approved by: re (Ken Smith), kib (mentor) 2009-03-29T08:07:36Z Dmitry Chagin dchagin@FreeBSD.org 2009-03-29T08:07:36Z urn:sha1:6363bdcad50bfe952364e2106777a38eedad7817 r189771: Implement new way of branding ELF binaries by looking to a ".note.ABI-tag" section. The search order of a brand is changed, now first of all the ".note.ABI-tag" is looked through. Move code which fetch osreldate for ELF binary to check_note() handler. r189919: Use the properly sized types for ELF object header and program headers. This fixes osrel fetching from the FreeBSD branding note for the 64bit platforms (bug introduced by r189771). r190264: Fix several issues with parsing the notes for ELF objects. Badly formed ELF note may cause the caclulated pointer to the next note to point both after the note region, that was checked in the code, but also to point before the region, that was not checked [1]. Remember the first note location in note0 and leap out if the note is not between note0 and note_end. In the similar way, badly formed note may cause infinite loop by pointing next note into the same or previous note. Guard against this by limiting amount of loop iterations by arbitrary choosen big number. For clarity, check the calculated note alignment in each iteration. PR: kern/132886 Approved by: re(Ken Smith) 2009-03-10T18:57:10Z John Baldwin jhb@FreeBSD.org 2009-03-10T18:57:10Z urn:sha1:772cc2acbf3dda4f332de34d7fd26a14bb2821dc itself. This also includes changes to the ia64 machine check code to defer adding machine check records to the sysctl tree, removing Giant from the CAM code that created dynamic sysctls, and tweaking the teardown of da(4) and cd(4) peripheral devices to not hold locks when freeing the sysctl tree. 2009-02-26T20:38:37Z John Baldwin jhb@FreeBSD.org 2009-02-26T20:38:37Z urn:sha1:00c57557ed7e69bf05f0900d4c769b902be353f5 implement pmap-level support for superpages. Pointy hat to: jhb 2009-02-26T15:59:22Z John Baldwin jhb@FreeBSD.org 2009-02-26T15:59:22Z urn:sha1:15826f991ff92f0afe64311327d5a2f38aae5cbf superpage reservation system to the machine-independent VM system as well as changes to the pmap code for amd64 and i386 to support superpages. Reviewed by: alc Tested by: ps 2009-01-09T11:09:57Z Konstantin Belousov kib@FreeBSD.org 2009-01-09T11:09:57Z urn:sha1:c9c68007085b418627c299949979de16dee7233b Change the static struct sysentvec and struct Elf_Brandinfo initializers to the C99 style. Explicitely initialize sysentvec.sv_maxssiz that was missed in most sysvecs. 2008-12-01T17:40:57Z Marcel Moolenaar marcel@FreeBSD.org 2008-12-01T17:40:57Z urn:sha1:c8b8aaa5e3c98ccbb26a9e065e2c1239f90c12be Work-around a compiler optimization bug, that broke libthr. Massive inlining resulted in constant propagation to the extend that cmpval was known to the compiler to be URWLOCK_WRITE_OWNER (= 0x80000000U). Unfortunately, instead of zero-extending the unsigned constant, it was sign-extended. As such, the cmpxchg instruction was comparing 0x0000000080000000LU to 0xffffffff80000000LU and obviously didn't perform the exchange. But, since the value returned by cmpxhg equalled cmpval (when zero- extended), the _thr_rtld_lock_release() function thought the exchange did happen and as such returned as if having released the lock. This was not the case. Subsequent locking requests found rw_state non-zero and the thread in question entered the kernel and block indefinitely. The work-around is to zero-extend by casting to uint64_t. Approved by: re (kensmith) 2008-08-27T04:41:15Z John Birrell jb@FreeBSD.org 2008-08-27T04:41:15Z urn:sha1:144cd58d16b601d52d00c5a37c8e0226aa1ce55a DTrace support. Note that this defaults the 'make buildkernel' to build with CTF data so that the release kernel and modules are DTrace-able. 2008-08-26T17:48:10Z John Baldwin jhb@FreeBSD.org 2008-08-26T17:48:10Z urn:sha1:8fa62068c24863225169a97c4c01bbaa8103fa89