Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1726713

ORC unwinder and 'reliable' flag to printk_stack_address()

From Jiri Kosina <jikos@kernel.org>
Newsgroups linux.kernel
Subject ORC unwinder and 'reliable' flag to printk_stack_address()
Date 2017-09-05 15:20 +0200
Message-ID <umlVL-34Y-9@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Josh,

I just got the below stack trace with current Linus' tree with ORC 
unwinder enabled:

	[    8.652765] Call Trace:
	[    8.652767]  dump_stack+0x7c/0xbf
	[    8.652769]  print_circular_bug+0x2d3/0x2e0
	[    8.652771]  check_prev_add+0x666/0x700
	[    8.652772]  ? print_bfs_bug+0x40/0x40
	[    8.652775]  lock_commit_crosslock+0x3f1/0x570
	[    8.652777]  complete+0x24/0x60
	[    8.652779]  __kthread_parkme+0x42/0x90
	[    8.652780]  smpboot_thread_fn+0x92/0x210
	[    8.652782]  kthread+0x145/0x180
	[    8.652783]  ? sort_range+0x20/0x20
	[    8.652785]  ? kthread_create_on_node+0x40/0x40
	[    8.652787]  ret_from_fork+0x2a/0x40

Please note the kthread_create_on_node(), sort_range() and print_bfs_bug() 
entries ... I believe they actually shouldn't be there at all. All of them 
are at the last byte belonging to the function. Am I missing something?

Thanks,

-- 
Jiri Kosina
SUSE Labs

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

ORC unwinder and 'reliable' flag to printk_stack_address() Jiri Kosina <jikos@kernel.org> - 2017-09-05 15:20 +0200
  Re: ORC unwinder and 'reliable' flag to printk_stack_address() Josh Poimboeuf <jpoimboe@redhat.com> - 2017-09-07 00:40 +0200
    Re: ORC unwinder and 'reliable' flag to printk_stack_address() Jiri Kosina <jikos@kernel.org> - 2017-09-08 13:20 +0200
      Re: ORC unwinder and 'reliable' flag to printk_stack_address() Josh Poimboeuf <jpoimboe@redhat.com> - 2017-09-08 15:20 +0200

csiph-web