From: kernel test robot <oliver.sang@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <linux-bcachefs@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [bcachefs] 2adfa46734: BUG:sleeping_function_called_from_invalid_context_at_include/linux/sched/mm.h
Date: Mon, 7 Apr 2025 12:45:26 +0800 [thread overview]
Message-ID: <202504071013.cd2f0072-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "BUG:sleeping_function_called_from_invalid_context_at_include/linux/sched/mm.h" on:
commit: 2adfa467347f6e5d8091ecbc45a78cac3d2a2b91 ("bcachefs: btree node write errors now print btree node")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master acc4d5ff0b61eb1715c498b6536c38c1feb7f3c1]
[test failed on linux-next/master fefb886b1344e222b3218f3c0165b0fd770e8b88]
in testcase: xfstests
version: xfstests-x86_64-8467552f-1_20241215
with following parameters:
disk: 4HDD
fs: bcachefs
test: generic-347
config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202504071013.cd2f0072-lkp@intel.com
[ 168.038599][ T12] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:321
[ 168.047979][ T12] in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 12, name: kworker/u16:0
[ 168.057027][ T12] preempt_count: 0, expected: 0
[ 168.061780][ T12] RCU nest depth: 1, expected: 0
[ 168.066620][ T12] CPU: 3 UID: 0 PID: 12 Comm: kworker/u16:0 Tainted: G I 6.14.0-rc6-00187-g2adfa467347f #1
[ 168.066626][ T12] Tainted: [I]=FIRMWARE_WORKAROUND
[ 168.066627][ T12] Hardware name: Dell Inc. OptiPlex 7040/0Y7WYT, BIOS 1.1.1 10/07/2015
[ 168.066646][ T12] Workqueue: dm-thin do_no_space_timeout [dm_thin_pool]
[ 168.066660][ T12] Call Trace:
[ 168.066662][ T12] <TASK>
[ 168.066665][ T12] dump_stack_lvl (lib/dump_stack.c:123 (discriminator 1))
[ 168.066671][ T12] __might_resched (kernel/sched/core.c:8768)
[ 168.066677][ T12] ? error_retry_list_with_code (include/linux/bio.h:578 drivers/md/dm-thin.c:599 drivers/md/dm-thin.c:616 drivers/md/dm-thin.c:656) dm_thin_pool
[ 168.066686][ T12] ? process_one_work (kernel/workqueue.c:3238)
[ 168.066691][ T12] __kmalloc_node_track_caller_noprof (include/linux/kernel.h:73 include/linux/sched/mm.h:321 include/linux/sched/mm.h:316 mm/slub.c:4066 mm/slub.c:4144 mm/slub.c:4293 mm/slub.c:4313)
[ 168.066710][ T12] ? vsnprintf (lib/vsprintf.c:2786)
[ 168.066715][ T12] ? bch2_printbuf_make_room (fs/bcachefs/printbuf.c:61 (discriminator 11)) bcachefs
[ 168.066936][ T12] ? krealloc_noprof (mm/slub.c:4820 mm/slub.c:4873)
[ 168.066940][ T12] krealloc_noprof (mm/slub.c:4820 mm/slub.c:4873)
[ 168.066943][ T12] ? time_stats_update_one (fs/bcachefs/time_stats.c:95) bcachefs
[ 168.067078][ T12] bch2_printbuf_make_room (fs/bcachefs/printbuf.c:61 (discriminator 11)) bcachefs
[ 168.067202][ T12] bch2_prt_printf (fs/bcachefs/printbuf.c:185 (discriminator 1)) bcachefs
[ 168.067325][ T12] ? __bch2_time_stats_update (fs/bcachefs/time_stats.c:130) bcachefs
[ 168.067456][ T12] ? __pfx_bch2_prt_printf (fs/bcachefs/printbuf.c:177) bcachefs
[ 168.067577][ T12] ? __pfx_bch2_latency_acct (fs/bcachefs/io_write.c:72) bcachefs
[ 168.067695][ T12] ? rcu_segcblist_enqueue (arch/x86/include/asm/atomic64_64.h:25 include/linux/atomic/atomic-arch-fallback.h:2672 include/linux/atomic/atomic-long.h:121 include/linux/atomic/atomic-instrumented.h:3261 kernel/rcu/rcu_segcblist.c:214 kernel/rcu/rcu_segcblist.c:231 kernel/rcu/rcu_segcblist.c:332)
[ 168.067700][ T12] ? queue_work_on (arch/x86/include/asm/bitops.h:137 include/asm-generic/bitops/instrumented-atomic.h:72 kernel/workqueue.c:2390)
[ 168.067704][ T12] btree_node_write_endio (fs/bcachefs/btree_io.c:2148) bcachefs
[ 168.067805][ T12] ? __pfx_btree_node_write_endio (fs/bcachefs/btree_io.c:2132) bcachefs
[ 168.067939][ T12] ? kmem_cache_free (mm/slub.c:2318 mm/slub.c:4609 mm/slub.c:4711)
[ 168.067943][ T12] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162)
[ 168.067948][ T12] ? __dm_io_complete (drivers/md/dm.c:967) dm_mod
[ 168.067972][ T12] ? __dm_io_complete (drivers/md/dm.c:967) dm_mod
[ 168.068004][ T12] ? bio_endio (block/bio.c:1543)
[ 168.068009][ T12] clone_endio (drivers/md/dm.c:1053 drivers/md/dm.c:1049 drivers/md/dm.c:1073 drivers/md/dm.c:1162) dm_mod
[ 168.068029][ T12] ? __pfx_clone_endio (drivers/md/dm.c:1107) dm_mod
[ 168.068049][ T12] ? _raw_spin_lock_irq (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:120 kernel/locking/spinlock.c:170)
[ 168.068052][ T12] ? __pfx__raw_spin_lock_irq (kernel/locking/spinlock.c:169)
[ 168.068054][ T12] ? __pfx_event_callback (drivers/md/dm.c:2397) dm_mod
[ 168.068075][ T12] error_retry_list_with_code (include/linux/bio.h:578 drivers/md/dm-thin.c:599 drivers/md/dm-thin.c:616 drivers/md/dm-thin.c:656) dm_thin_pool
[ 168.068085][ T12] process_one_work (kernel/workqueue.c:3238)
[ 168.068090][ T12] worker_thread (kernel/workqueue.c:3313 kernel/workqueue.c:3400)
[ 168.068096][ T12] ? __pfx_worker_thread (kernel/workqueue.c:3346)
[ 168.068099][ T12] kthread (kernel/kthread.c:464)
[ 168.068102][ T12] ? __pfx_kthread (kernel/kthread.c:413)
[ 168.068105][ T12] ? __pfx__raw_spin_lock_irq (kernel/locking/spinlock.c:169)
[ 168.068108][ T12] ? __pfx_kthread (kernel/kthread.c:413)
[ 168.068111][ T12] ret_from_fork (arch/x86/kernel/process.c:148)
[ 168.068115][ T12] ? __pfx_kthread (kernel/kthread.c:413)
[ 168.068117][ T12] ret_from_fork_asm (arch/x86/entry/entry_64.S:257)
[ 168.068124][ T12] </TASK>
[ 168.321126][ T12] bcachefs (dm-3): btree write error: critical space allocation
[ 168.321126][ T12] alloc level 1/0
[ 168.321126][ T12] u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq 930249c94ccac572 written 1 min_key POS_MIN durability: 1 ptr: 0:254:0 gen 0
[ 168.345920][ T68] bcachefs (dm-3): btree_node_write_work(): fatal error writing btree node: btree_node_write_all_failed
[ 168.345920][ T68] alloc level 1/0
[ 168.345920][ T68] u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq 930249c94ccac572 written 1 min_key POS_MIN durability: 1 ptr: 0:254:0 gen 0
[ 168.346967][ T12] bcachefs (dm-3): btree write error: critical space allocation
[ 168.346967][ T12] alloc level 0/0
[ 168.346967][ T12] u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c8440b093e7b4819 written 146 min_key 0:1285:1 durability: 1 ptr: 0:255:0 gen 0
[ 168.374052][ T68] bcachefs (dm-3): fatal error - emergency read only
[ 168.405579][ T83] bcachefs (dm-3): btree_node_write_work(): fatal error writing btree node: btree_node_write_all_failed
[ 168.405579][ T83] alloc level 0/0
[ 168.405579][ T83] u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c8440b093e7b4819 written 146 min_key 0:1285:1 durability: 1 ptr: 0:255:0 gen 0
[ 168.406960][ T12] bcachefs (dm-3 inum 4579 offset 524288): data write error: critical space allocation
[ 168.443825][ T12] bcachefs (dm-3 inum 4579 offset 786432): data write error: critical space allocation
[ 168.459843][ T141] bcachefs (dm-3): unclean shutdown complete, journal seq 532
[ 168.856214][ T3526] device-mapper: thin: Data device (dm-1) discard unsupported: Disabling discard passdown.
[ 168.867365][ T3526] device-mapper: thin: 253:2: switching pool to write mode
[ 168.875526][ T3526] device-mapper: thin: 253:2: growing the data device from 1000 to 1200 blocks
[ 171.218727][ T3618] bcachefs (sda1): clean shutdown complete, journal seq 34
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250407/202504071013.cd2f0072-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-07 4:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202504071013.cd2f0072-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.