From: kernel test robot <lkp@intel.com>
To: Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH 12/31] btrfs: move the core extent_io_tree code into extent-io-tree.c
Date: Sat, 3 Sep 2022 14:28:56 +0800 [thread overview]
Message-ID: <202209031411.pvUL5nPj-lkp@intel.com> (raw)
In-Reply-To: <c534c12c1dcf0821971b8918abced08aafd27055.1662149276.git.josef@toxicpanda.com>
Hi Josef,
I love your patch! Perhaps something to improve:
[auto build test WARNING on kdave/for-next]
[also build test WARNING on next-20220901]
[cannot apply to rostedt-trace/for-next linus/master v6.0-rc3]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Josef-Bacik/btrfs-move-extent_io_tree-code-and-cleanups/20220903-042359
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20220903/202209031411.pvUL5nPj-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/9fa98f420ce2ac5220d35bedf881d5e6bbd18e9d
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Josef-Bacik/btrfs-move-extent_io_tree-code-and-cleanups/20220903-042359
git checkout 9fa98f420ce2ac5220d35bedf881d5e6bbd18e9d
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=alpha SHELL=/bin/bash fs/btrfs/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/btrfs/extent-io-tree.c:237: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Search @tree for an entry that contains @offset. Such entry would have
fs/btrfs/extent-io-tree.c:298: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Search offset in the tree or fill neighbor rbtree node pointers.
fs/btrfs/extent-io-tree.c:1393: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Find a contiguous area of bits
fs/btrfs/extent-io-tree.c:1431: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Find the first range that has @bits not set. This range could start before
vim +237 fs/btrfs/extent-io-tree.c
235
236 /**
> 237 * Search @tree for an entry that contains @offset. Such entry would have
238 * entry->start <= offset && entry->end >= offset.
239 *
240 * @tree: the tree to search
241 * @offset: offset that should fall within an entry in @tree
242 * @node_ret: pointer where new node should be anchored (used when inserting an
243 * entry in the tree)
244 * @parent_ret: points to entry which would have been the parent of the entry,
245 * containing @offset
246 *
247 * Return a pointer to the entry that contains @offset byte address and don't change
248 * @node_ret and @parent_ret.
249 *
250 * If no such entry exists, return pointer to entry that ends before @offset
251 * and fill parameters @node_ret and @parent_ret, ie. does not return NULL.
252 */
253 static inline struct rb_node *tree_search_for_insert(struct extent_io_tree *tree,
254 u64 offset,
255 struct rb_node ***node_ret,
256 struct rb_node **parent_ret)
257 {
258 struct rb_root *root = &tree->state;
259 struct rb_node **node = &root->rb_node;
260 struct rb_node *prev = NULL;
261 struct tree_entry *entry;
262
263 while (*node) {
264 prev = *node;
265 entry = rb_entry(prev, struct tree_entry, rb_node);
266
267 if (offset < entry->start)
268 node = &(*node)->rb_left;
269 else if (offset > entry->end)
270 node = &(*node)->rb_right;
271 else
272 return *node;
273 }
274
275 if (node_ret)
276 *node_ret = node;
277 if (parent_ret)
278 *parent_ret = prev;
279
280 /* Search neighbors until we find the first one past the end */
281 while (prev && offset > entry->end) {
282 prev = rb_next(prev);
283 entry = rb_entry(prev, struct tree_entry, rb_node);
284 }
285
286 return prev;
287 }
288
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-09-03 6:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 20:16 [PATCH 00/31] btrfs: move extent_io_tree code and cleanups Josef Bacik
2022-09-02 20:16 ` [PATCH 01/31] btrfs: cleanup clean_io_failure Josef Bacik
2022-09-05 12:27 ` Johannes Thumshirn
2022-09-07 18:51 ` David Sterba
2022-09-02 20:16 ` [PATCH 02/31] btrfs: unexport internal failrec functions Josef Bacik
2022-09-02 20:16 ` [PATCH 03/31] btrfs: stop using extent_io_tree for io_failure_record's Josef Bacik
2022-09-07 18:53 ` David Sterba
2022-09-02 20:16 ` [PATCH 04/31] btrfs: use find_first_extent_bit in btrfs_clean_io_failure Josef Bacik
2022-09-02 20:16 ` [PATCH 05/31] btrfs: separate out the extent state and extent buffer init code Josef Bacik
2022-09-02 20:16 ` [PATCH 06/31] btrfs: separate out the eb and extent state leak helpers Josef Bacik
2022-09-02 20:16 ` [PATCH 07/31] btrfs: temporarily export alloc_extent_state helpers Josef Bacik
2022-09-02 20:16 ` [PATCH 08/31] btrfs: move extent state init and alloc functions to their own file Josef Bacik
2022-09-02 20:16 ` [PATCH 09/31] btrfs: convert BUG_ON(EXTENT_BIT_LOCKED) checks to ASSERT's Josef Bacik
2022-09-07 18:57 ` David Sterba
2022-09-02 20:16 ` [PATCH 10/31] btrfs: move simple extent bit helpers out of extent_io.c Josef Bacik
2022-09-02 20:16 ` [PATCH 11/31] btrfs: export wait_extent_bit Josef Bacik
2022-09-02 20:16 ` [PATCH 12/31] btrfs: move the core extent_io_tree code into extent-io-tree.c Josef Bacik
2022-09-03 6:28 ` kernel test robot [this message]
2022-09-07 19:03 ` David Sterba
2022-09-02 20:16 ` [PATCH 13/31] btrfs: remove struct tree_entry Josef Bacik
2022-09-02 20:16 ` [PATCH 14/31] btrfs: use next_state instead of rb_next where we can Josef Bacik
2022-09-02 20:16 ` [PATCH 15/31] btrfs: make tree_search return struct extent_state Josef Bacik
2022-09-02 20:16 ` [PATCH 16/31] btrfs: make tree_search_for_insert return extent_state Josef Bacik
2022-09-02 20:16 ` [PATCH 17/31] btrfs: make tree_search_prev_next return extent_state's Josef Bacik
2022-09-02 20:16 ` [PATCH 18/31] btrfs: use next_state/prev_state in merge_state Josef Bacik
2022-09-02 20:16 ` [PATCH 19/31] btrfs: remove temporary exports for extent_state movement Josef Bacik
2022-09-02 20:16 ` [PATCH 20/31] btrfs: move irrelevant prototypes to their appropriate header Josef Bacik
2022-09-02 20:16 ` [PATCH 21/31] btrfs: drop exclusive_bits from set_extent_bit Josef Bacik
2022-09-02 20:16 ` [PATCH 22/31] btrfs: remove the wake argument from clear_extent_bits Josef Bacik
2022-09-02 20:16 ` [PATCH 23/31] btrfs: remove failed_start argument from set_extent_bit Josef Bacik
2022-09-02 20:16 ` [PATCH 24/31] btrfs: drop extent_changeset " Josef Bacik
2022-09-02 20:16 ` [PATCH 25/31] btrfs: unify the lock/unlock extent variants Josef Bacik
2022-09-02 20:16 ` [PATCH 26/31] btrfs: get rid of track_uptodate Josef Bacik
2022-09-07 18:47 ` David Sterba
2022-09-02 20:16 ` [PATCH 27/31] btrfs: get rid of ->dirty_bytes Josef Bacik
2022-09-07 18:48 ` David Sterba
2022-09-02 20:16 ` [PATCH 28/31] btrfs: don't clear CTL bits when trying to release extent state Josef Bacik
2022-09-02 20:16 ` [PATCH 29/31] btrfs: replace delete argument with EXTENT_CLEAR_ALL_BITS Josef Bacik
2022-09-02 20:16 ` [PATCH 30/31] btrfs: don't init io tree with private data for non inodes Josef Bacik
2022-09-02 20:16 ` [PATCH 31/31] btrfs: remove is_data_inode() checks in extent-io-tree.c Josef Bacik
2022-09-06 18:30 ` [PATCH 00/31] btrfs: move extent_io_tree code and cleanups David Sterba
2022-09-07 18:42 ` David Sterba
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=202209031411.pvUL5nPj-lkp@intel.com \
--to=lkp@intel.com \
--cc=josef@toxicpanda.com \
--cc=kbuild-all@lists.01.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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