On 10/26/15 9:39 , Richard PALO wrote: > I just set kmem_flags = 0xf in /etc/system and rebooted. > > Now, immediately after reboot I already see: >> richard@omnis:/home/richard$ echo ::kmem_verify|pfexec mdb -k >> Cache Name Addr Cache Integrity >> ... >> kmem_bufctl_audit_cache ffffff0900424a88 8 corrupt buffers >> ... >> streams_dblk_80 ffffff090043ea88 1 corrupt buffer >> ...
While I haven't looked at the exact implementation of ::kmem_verify, I am rather skeptical it could ever work for a live system with mdb -k. It's not like the kernel is stopping when you're reading something like this, so it's clearly going to be racy. If you dumped the system and then looked at the ::kmem_verify when the system was static, or you used kmdb to pause the system and run the ::kmem_verify, I think you'll get a much more realistic answer. Robert >> richard@omnis:/home/richard$ echo >> "ffffff0900424a88::whatis;ffffff090043ea88::whatis" |pfexec mdb -k >> ffffff0900424a88 is allocated from the kmem_cache vmem arena: >> ADDR TYPE START END SIZE >> THREAD TIMESTAMP >> ffffff090040ccb8 ALLC ffffff0900424a88 ffffff0900424fc0 1336 >> fffffffffbc3da60 0 >> vmem_hash_insert+0xae >> vmem_seg_alloc+0x23e >> vmem_xalloc+0x749 >> kmem_cache_create+0xdf >> kmem_cache_init+0x162 >> kmem_init+0x3ae >> startup_kmem+0xbf >> startup+0x3f >> main+0x9b >> _locore_start+0x90 >> >> ffffff090043ea88 is allocated from the kmem_cache vmem arena: >> ADDR TYPE START END SIZE >> THREAD TIMESTAMP >> ffffff0900452ae8 ALLC ffffff090043ea88 ffffff090043efc0 1336 >> fffffffffbc3da60 0 >> vmem_hash_insert+0xae >> vmem_seg_alloc+0x23e >> vmem_xalloc+0x749 >> kmem_cache_create+0xdf >> streams_msg_init+0x10f >> kmem_init+0x42b >> startup_kmem+0xbf >> startup+0x3f >> main+0x9b >> _locore_start+0x90 >> > > Just launched a gate build, after a few minutes already: >> richard@omnis:/home/richard$ echo ::kmem_verify|pfexec mdb -k >> Cache Name Addr Cache Integrity >> ... >> kmem_slab_cache ffffff0900424008 2 corrupt buffers >> kmem_bufctl_cache ffffff0900424548 clean >> kmem_bufctl_audit_cache ffffff0900424a88 9 corrupt buffers >> kmem_alloc_8 ffffff0900428a88 69 corrupt buffers >> kmem_alloc_16 ffffff090042a008 19 corrupt buffers >> kmem_alloc_24 ffffff090042a548 14 corrupt buffers >> kmem_alloc_32 ffffff090042aa88 170 corrupt buffers >> kmem_alloc_40 ffffff090042b008 17 corrupt buffers >> kmem_alloc_48 ffffff090042b548 147 corrupt buffers >> kmem_alloc_56 ffffff090042ba88 57 corrupt buffers >> kmem_alloc_64 ffffff090042c008 143 corrupt buffers >> kmem_alloc_80 ffffff090042c548 91 corrupt buffers >> kmem_alloc_96 ffffff090042ca88 14 corrupt buffers >> kmem_alloc_112 ffffff090042e008 19 corrupt buffers >> kmem_alloc_128 ffffff090042e548 1 corrupt buffer >> kmem_alloc_160 ffffff090042ea88 2 corrupt buffers >> kmem_alloc_192 ffffff090042f008 3 corrupt buffers >> kmem_alloc_224 ffffff090042f548 clean >> kmem_alloc_256 ffffff090042fa88 clean >> kmem_alloc_320 ffffff0900430008 clean >> kmem_alloc_384 ffffff0900430548 3 corrupt buffers >> ... >> streams_mblk ffffff090043e008 1 corrupt buffer >> streams_dblk_16 ffffff090043e548 clean >> streams_dblk_80 ffffff090043ea88 1 corrupt buffer >> ... >> seg_cache ffffff09534f2008 12 corrupt buffers >> ... >> thread_cache ffffff09575bca88 2 corrupt buffers >> lwp_cache ffffff0958691008 clean >> turnstile_cache ffffff0958691548 clean >> tslabel_cache ffffff0958691a88 clean >> cred_cache ffffff09586b6008 clean >> rctl_cache ffffff09586b6548 22 corrupt buffers >> rctl_val_cache ffffff09586b6a88 257 corrupt buffers >> ... >> vn_cache ffffff0958991548 40 corrupt buffers >> vsk_anchor_cache ffffff0958991a88 clean >> file_cache ffffff0958993008 7 corrupt buffers >> ... >> as_cache ffffff0958996a88 1 corrupt buffer >> marker_cache ffffff0958997008 clean >> anon_cache ffffff0958997548 11796 corrupt buffers >> anonmap_cache ffffff0958997a88 79 corrupt buffers >> segvn_cache ffffff095899a008 125 corrupt buffers >> ... >> range_seg_cache ffffff09589d2548 2 corrupt buffers >> zio_cache ffffff09589d2a88 clean >> zio_link_cache ffffff09589d3008 clean >> zio_buf_512 ffffff09589d3548 6 corrupt buffers >> zio_buf_1024 ffffff09589d4008 clean >> zio_buf_1536 ffffff09589d4a88 clean >> sa_cache ffffff095a04fa88 22 corrupt buffers >> dnode_t ffffff095a050008 clean >> dmu_buf_impl_t ffffff095a050548 1 corrupt buffer >> arc_buf_hdr_t_full ffffff095a050a88 clean >> arc_buf_hdr_t_l2only ffffff095a053008 clean >> arc_buf_t ffffff095a053548 2 corrupt buffers >> zil_lwb_cache ffffff095a053a88 clean >> zfs_znode_cache ffffff09588fe008 2 corrupt buffers >> ... > ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
