lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 10 Oct 2013 20:50:03 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Minchan Kim <minchan@...nel.org>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	Dave Chinner <dchinner@...hat.com>,
	Linux FS devel list <linux-fsdevel@...r.kernel.org>,
	"xfs@....sgi.com" <xfs@....sgi.com>
Subject: [zram] WARNING: CPU: 0 PID: 361 at lib/debugobjects.c:260
 debug_print_object()

[[
   Dave and XFS folks: we seem to find the real culprit this time.

   Minchan, hopefully you are the right one to look for. I caught
   the wrong people and went through hard times.. :-)
]]

Greetings,

I got the below dmesg and the first bad commit is

commit 0231c403bb065307493fe997ad170487b4d55eb8
Author: Minchan Kim <minchan@...nel.org>
Date:   Wed Jan 30 11:41:40 2013 +0900

    zram: force disksize setting before using zram
    
    Now zram document syas "set disksize is optional"
    but partly it's wrong. When you try to use zram firstly after
    booting, you must set disksize, otherwise zram can't work because
    zram gendisk's size is 0. But once you do it, you can use zram freely
    after reset because reset doesn't reset to zero paradoxically.
    So in this time, disksize setting is optional.:(
    It's inconsitent for user behavior and not straightforward.
    
    This patch forces always setting disksize firstly before using zram.
    Yes. It changes current behavior so someone could complain when
    he upgrades zram. Apparently it could be a problem if zram is mainline
    but it still lives in staging so behavior could be changed for right
    way to go. Let them excuse.
    
    Acked-by: Jerome Marchand <jmarchand@...hat.com>
    Acked-by: Nitin Gupta <ngupta@...are.org>
    Acked-by: Dan Magenheimer <dan.magenheimer@...cle.com>
    Signed-off-by: Minchan Kim <minchan@...nel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>

[   35.635867] qnx6: unable to set blocksize
[   35.638410] ADFS-fs error (device zram0): adfs_fill_super: unable to read superblock
[   35.662564] ------------[ cut here ]------------
[   35.664652] WARNING: CPU: 0 PID: 361 at lib/debugobjects.c:260 debug_print_object+0x94/0xa2()
[   35.669001] ODEBUG: free active (active state 0) object type: work_struct hint: xfs_buf_iodone_work+0x0/0xfe
[   35.670149] CPU: 0 PID: 361 Comm: mount Not tainted 3.12.0-rc2-next-20130927-03100-ga0cf1ab #3
[   35.670149]  00000000 00000000 8a299d30 8275c9a2 8a299d70 00000000 00000104 8a299d60
[   35.670149]  8103f5e3 8334fafe 8a299d8c 00000169 8334fb3b 00000104 817001fb 817001fb
[   35.670149]  8a73ebd8 8355b58c 83323588 8a299d78 8103f641 00000009 8a299d70 8334fafe
[   35.670149] Call Trace:
[   35.670149]  [<8275c9a2>] dump_stack+0x7a/0xaa
[   35.670149]  [<8103f5e3>] warn_slowpath_common+0x8c/0xa3
[   35.670149]  [<817001fb>] ? debug_print_object+0x94/0xa2
[   35.670149]  [<817001fb>] ? debug_print_object+0x94/0xa2
[   35.670149]  [<8103f641>] warn_slowpath_fmt+0x2e/0x30
[   35.670149]  [<817001fb>] debug_print_object+0x94/0xa2
[   35.670149]  [<81344703>] ? xfs_buf_unlock+0x17f/0x17f
[   35.670149]  [<81700f1a>] debug_check_no_obj_freed+0xe2/0x1f8
[   35.670149]  [<8115aaa1>] kmem_cache_free+0xfe/0x32b
[   35.670149]  [<81342be0>] xfs_buf_free+0x263/0x26f
[   35.670149]  [<81343a71>] xfs_buf_rele+0x3e0/0x3f0
[   35.670149]  [<813635f6>] ? xfs_readsb+0x25e/0x268
[   35.670149]  [<813635f6>] xfs_readsb+0x25e/0x268
[   35.670149]  [<827243a5>] ? register_cpu_notifier+0x20/0x27
[   35.670149]  [<81367344>] xfs_fs_fill_super+0x27d/0x495
[   35.670149]  [<813670c7>] ? xfs_finish_flags+0x24e/0x24e
[   35.670149]  [<811666bf>] mount_bdev+0x1d6/0x256
[   35.670149]  [<813670c7>] ? xfs_finish_flags+0x24e/0x24e
[   35.670149]  [<8115a80b>] ? __kmalloc_track_caller+0x21a/0x3b2
[   35.670149]  [<816d87d6>] ? ida_get_new_above+0x24a/0x25b
[   35.670149]  [<81364b69>] xfs_fs_mount+0x1a/0x1f
[   35.670149]  [<813670c7>] ? xfs_finish_flags+0x24e/0x24e
[   35.670149]  [<81166a09>] mount_fs+0x38/0x1b3
[   35.670149]  [<811395a4>] ? __alloc_percpu+0xa/0xc
[   35.670149]  [<8118b7ff>] ? alloc_vfsmnt+0x108/0x1d6
[   35.670149]  [<8118ca68>] vfs_kern_mount+0x97/0x123
[   35.670149]  [<8118ef8f>] do_mount+0xc8e/0xe0d
[   35.670149]  [<8118e2e3>] ? copy_mount_string+0x51/0x6f
[   35.670149]  [<8118f1ee>] SyS_mount+0xe0/0x10d
[   35.670149]  [<827889ff>] syscall_call+0x7/0xb
[   35.670149] ---[ end trace d814169ab0ed4dd3 ]---
[   35.670149] BUG: sleeping function called from invalid context at kernel/workqueue.c:2810

git bisect start v3.9 v3.8 --
git bisect  bad d778df51c09264076fe0208c099ef7d428f21790  # 14:59      0-      2  mm: vmscan: save work scanning (almost) empty LRU lists
git bisect good 3278bb748d2437eb1464765f36429e5d6aa91c38  # 15:45     26+      4  ocfs2: unlock super lock if lockres refresh failed
git bisect  bad b5c78e04dd061b776978dad61dd85357081147b0  # 16:02      0-      1  Merge tag 'staging-3.9-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
git bisect  bad 4d1b2fbbaf6420f64fae8b3f3a7801fc97d07260  # 16:25      0-     13  staging/ozwpan: Fix NULL vs zero in ozusbsvc1.c (sparse warning)
git bisect good 934efe63e8bece28c69d18ea5e3bfd1619fc23b2  # 17:02     26+      0  staging: comedi: addi_apci_2200: use addi_watchdog module
git bisect good 6a6df2d9113856a4371ca4f1cb29221790320307  # 17:26     26+      0  Partially revert "staging:iio:gyro:adxrs450 make more use of spi_read and spi_write."
git bisect  bad 4e98fcfb95dfd9c40976dcfa2f3b878eeec4dbaa  # 17:41      0-      7  Merge tag 'iio-for-3.9c' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next
git bisect  bad a5e080b83e28f2b67c198cb3be96f4b190522109  # 18:04      0-      7  staging/xgifb: remove unnecessary temp variable in XGIfb_mode_rate_to_ddata
git bisect good 42d1aeea844874961af00621f0a5584aa9b9e1a5  # 18:27     26+      0  staging: comedi: ni_mio_cs: convert to auto attach
git bisect good de06d7c6b8e3b886eec0302ecbadf76944a42ca4  # 18:44     26+      0  staging: comedi: restrict comedi_set_hw_dev() usage
git bisect  bad 3de738cd30306f754ea35d35b5dad29fdbec84c9  # 19:04      0-      2  zram: give up lazy initialization of zram metadata
git bisect good 7f70410fe03f9f31a99bb5074b5e3c48f3b90541  # 19:17     26+      0  pci_ids.h: add common pci vendor ids from comedi subsystem
git bisect  bad 0231c403bb065307493fe997ad170487b4d55eb8  # 19:26      7-      9  zram: force disksize setting before using zram
git bisect good 7e5a5104c6af709a8d97d5f4711e7c917761d464  # 19:46     27+      0  zram: Fix deadlock bug in partial read/write
git bisect good 7e5a5104c6af709a8d97d5f4711e7c917761d464  # 19:51     81+      0  zram: Fix deadlock bug in partial read/write
git bisect  bad a0cf1abc25ac197dd97b857c0f6341066a8cb1cf  # 19:52      0-     11  Add linux-next specific files for 20130927
git bisect  bad a0cf1abc25ac197dd97b857c0f6341066a8cb1cf  # 20:13      0-     11  Add linux-next specific files for 20130927

Thanks,
Fengguang

View attachment "dmesg-yocto-jaketown-25:20131004225448:i386-randconfig-j0-10042023:3.12.0-rc2-next-20130927-03100-ga0cf1ab:3" of type "text/plain" (78544 bytes)

Download attachment "bisect-a0cf1abc25ac197dd97b857c0f6341066a8cb1cf-i386-randconfig-j0-10042023-debug_print_object-38599.log" of type "application/octet-stream" (61247 bytes)

View attachment "config-3.12.0-rc2-next-20130927-03100-ga0cf1ab" of type "text/plain" (94515 bytes)

Powered by blists - more mailing lists