From: chenchangcheng <ccc194101@163.com>
To: jpoimboe@kernel.org, peterz@infradead.org
Cc: stable@vger.kernel.org, chenchangcheng <ccc194101@163.com>
Subject: [PATCH] objtool: add bch2_trans_unlocked_error to bcachefs noreturns.
Date: Wed, 18 Dec 2024 17:05:07 +0800 [thread overview]
Message-ID: <20241218090507.289846-1-ccc194101@163.com> (raw)
fs/bcachefs/btree_trans_commit.o: warning: objtool: bch2_trans_commit_write_locked.isra.0() falls through to next function do_bch2_trans_commit.isra.0()
fs/bcachefs/btree_trans_commit.o: warning: objtool: .text: unexpected end of section
......
fs/bcachefs/btree_update.o: warning: objtool: bch2_trans_update_get_key_cache() falls through to next function flush_new_cached_update()
fs/bcachefs/btree_update.o: warning: objtool: flush_new_cached_update() falls through to next function bch2_trans_update_by_path()
Signed-off-by: chenchangcheng <ccc194101@163.com>
---
tools/objtool/noreturns.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/objtool/noreturns.h b/tools/objtool/noreturns.h
index f37614cc2c1b..b2174894f9f7 100644
--- a/tools/objtool/noreturns.h
+++ b/tools/objtool/noreturns.h
@@ -19,6 +19,7 @@ NORETURN(__x64_sys_exit_group)
NORETURN(arch_cpu_idle_dead)
NORETURN(bch2_trans_in_restart_error)
NORETURN(bch2_trans_restart_error)
+NORETURN(bch2_trans_unlocked_error)
NORETURN(cpu_bringup_and_idle)
NORETURN(cpu_startup_entry)
NORETURN(do_exit)
--
2.25.1
next reply other threads:[~2024-12-18 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 9:05 chenchangcheng [this message]
2024-12-18 21:27 ` [PATCH] objtool: add bch2_trans_unlocked_error to bcachefs noreturns Josh Poimboeuf
2024-12-19 5:51 ` ccc194101
2024-12-19 22:58 ` Josh Poimboeuf
2024-12-19 22:59 ` Josh Poimboeuf
2024-12-20 1:27 ` ccc194101
2024-12-20 7:19 ` Greg KH
2024-12-20 7:22 ` ccc194101
-- strict thread matches above, loose matches on Subject: below --
2024-12-18 9:03 chenchangcheng
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=20241218090507.289846-1-ccc194101@163.com \
--to=ccc194101@163.com \
--cc=jpoimboe@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox