* [moderation/CI] Re: fs: rework inode reference counting
@ 2025-08-21 21:08 syzbot ci
0 siblings, 0 replies; 3+ messages in thread
From: syzbot ci @ 2025-08-21 21:08 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v1] fs: rework inode reference counting
https://lore.kernel.org/all/cover.1755806649.git.josef@toxicpanda.com
* [PATCH 01/50] fs: add an i_obj_count refcount to the inode
* [PATCH 02/50] fs: make the i_state flags an enum
* [PATCH 03/50] fs: hold an i_obj_count reference in wait_sb_inodes
* [PATCH 04/50] fs: hold an i_obj_count reference for the i_wb_list
* [PATCH 05/50] fs: hold an i_obj_count reference for the i_io_list
* [PATCH 06/50] fs: hold an i_obj_count reference in writeback_sb_inodes
* [PATCH 07/50] fs: hold an i_obj_count reference while on the hashtable
* [PATCH 08/50] fs: hold an i_obj_count reference while on the LRU list
* [PATCH 09/50] fs: hold an i_obj_count reference while on the sb inode list
* [PATCH 10/50] fs: stop accessing ->i_count directly in f2fs and gfs2
* [PATCH 11/50] fs: hold an i_obj_count when we have an i_count reference
* [PATCH 12/50] fs: rework iput logic
* [PATCH 13/50] fs: add an I_LRU flag to the inode
* [PATCH 14/50] fs: maintain a list of pinned inodes
* [PATCH 15/50] fs: delete the inode from the LRU list on lookup
* [PATCH 16/50] fs: change evict_inodes to use iput instead of evict directly
* [PATCH 17/50] fs: hold a full ref while the inode is on a LRU
* [PATCH 18/50] fs: disallow 0 reference count inodes
* [PATCH 19/50] fs: make evict_inodes add to the dispose list under the i_lock
* [PATCH 20/50] fs: convert i_count to refcount_t
* [PATCH 21/50] fs: use refcount_inc_not_zero in igrab
* [PATCH 22/50] fs: use inode_tryget in find_inode*
* [PATCH 23/50] fs: update find_inode_*rcu to check the i_count count
* [PATCH 24/50] fs: use igrab in insert_inode_locked
* [PATCH 25/50] fs: remove I_WILL_FREE|I_FREEING check from __inode_add_lru
* [PATCH 26/50] fs: remove I_WILL_FREE|I_FREEING check in inode_pin_lru_isolating
* [PATCH 27/50] fs: use inode_tryget in evict_inodes
* [PATCH 28/50] fs: change evict_dentries_for_decrypted_inodes to use refcount
* [PATCH 29/50] block: use igrab in sync_bdevs
* [PATCH 30/50] bcachefs: use the refcount instead of I_WILL_FREE|I_FREEING
* [PATCH 31/50] btrfs: don't check I_WILL_FREE|I_FREEING
* [PATCH 32/50] fs: use igrab in drop_pagecache_sb
* [PATCH 33/50] fs: stop checking I_FREEING in d_find_alias_rcu
* [PATCH 34/50] ext4: stop checking I_WILL_FREE|IFREEING in ext4_check_map_extents_env
* [PATCH 35/50] fs: remove I_WILL_FREE|I_FREEING from fs-writeback.c
* [PATCH 36/50] gfs2: remove I_WILL_FREE|I_FREEING usage
* [PATCH 37/50] fs: remove I_WILL_FREE|I_FREEING check from dquot.c
* [PATCH 38/50] notify: remove I_WILL_FREE|I_FREEING checks in fsnotify_unmount_inodes
* [PATCH 39/50] xfs: remove I_FREEING check
* [PATCH 40/50] landlock: remove I_FREEING|I_WILL_FREE check
* [PATCH 41/50] fs: change inode_is_dirtytime_only to use refcount
* [PATCH 42/50] btrfs: remove references to I_FREEING
* [PATCH 43/50] ext4: remove reference to I_FREEING in inode.c
* [PATCH 44/50] ext4: remove reference to I_FREEING in orphan.c
* [PATCH 45/50] pnfs: use i_count refcount to determine if the inode is going away
* [PATCH 46/50] fs: remove some spurious I_FREEING references in inode.c
* [PATCH 47/50] xfs: remove reference to I_FREEING|I_WILL_FREE
* [PATCH 48/50] ocfs2: do not set I_WILL_FREE
* [PATCH 49/50] fs: remove I_FREEING|I_WILL_FREE
* [PATCH 50/50] fs: add documentation explaining the reference count rules for inodes
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/743e203c-480a-40b0-a5b2-65be9b42c520
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 068a56e56fa81e42fc5f08dff34fab149bb60a09
arch: amd64
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
config: https://ci.syzbot.org/builds/43927ea0-33b7-4247-9afc-871999c47ee6/config
fs/smb/client/inode.c:2782:37: error: no member named 'counter' in 'struct refcount_struct'
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[brauner@kernel.org josef@toxicpanda.com kernel-team@fb.com linux-btrfs@vger.kernel.org linux-ext4@vger.kernel.org linux-fsdevel@vger.kernel.org linux-xfs@vger.kernel.org viro@zeniv.linux.org.uk]
If the report looks fine to you, reply with:
#syz upstream
^ permalink raw reply [flat|nested] 3+ messages in thread
* [moderation/CI] Re: fs: rework inode reference counting
@ 2025-08-26 20:57 syzbot ci
2025-08-27 8:02 ` Aleksandr Nogikh
0 siblings, 1 reply; 3+ messages in thread
From: syzbot ci @ 2025-08-26 20:57 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v2] fs: rework inode reference counting
https://lore.kernel.org/all/cover.1756222464.git.josef@toxicpanda.com
* [PATCH v2 01/54] fs: make the i_state flags an enum
* [PATCH v2 02/54] fs: add an icount_read helper
* [PATCH v2 03/54] fs: rework iput logic
* [PATCH v2 04/54] fs: add an i_obj_count refcount to the inode
* [PATCH v2 05/54] fs: hold an i_obj_count reference in wait_sb_inodes
* [PATCH v2 06/54] fs: hold an i_obj_count reference for the i_wb_list
* [PATCH v2 07/54] fs: hold an i_obj_count reference for the i_io_list
* [PATCH v2 08/54] fs: hold an i_obj_count reference in writeback_sb_inodes
* [PATCH v2 09/54] fs: hold an i_obj_count reference while on the hashtable
* [PATCH v2 10/54] fs: hold an i_obj_count reference while on the LRU list
* [PATCH v2 11/54] fs: hold an i_obj_count reference while on the sb inode list
* [PATCH v2 12/54] fs: stop accessing ->i_count directly in f2fs and gfs2
* [PATCH v2 13/54] fs: hold an i_obj_count when we have an i_count reference
* [PATCH v2 14/54] fs: add an I_LRU flag to the inode
* [PATCH v2 15/54] fs: maintain a list of pinned inodes
* [PATCH v2 16/54] fs: delete the inode from the LRU list on lookup
* [PATCH v2 17/54] fs: remove the inode from the LRU list on unlink/rmdir
* [PATCH v2 18/54] fs: change evict_inodes to use iput instead of evict directly
* [PATCH v2 19/54] fs: hold a full ref while the inode is on a LRU
* [PATCH v2 20/54] fs: disallow 0 reference count inodes
* [PATCH v2 21/54] fs: make evict_inodes add to the dispose list under the i_lock
* [PATCH v2 22/54] fs: convert i_count to refcount_t
* [PATCH v2 23/54] fs: use refcount_inc_not_zero in igrab
* [PATCH v2 24/54] fs: use inode_tryget in find_inode*
* [PATCH v2 25/54] fs: update find_inode_*rcu to check the i_count count
* [PATCH v2 26/54] fs: use igrab in insert_inode_locked
* [PATCH v2 27/54] fs: remove I_WILL_FREE|I_FREEING check from __inode_add_lru
* [PATCH v2 28/54] fs: remove I_WILL_FREE|I_FREEING check in inode_pin_lru_isolating
* [PATCH v2 29/54] fs: use inode_tryget in evict_inodes
* [PATCH v2 30/54] fs: change evict_dentries_for_decrypted_inodes to use refcount
* [PATCH v2 31/54] block: use igrab in sync_bdevs
* [PATCH v2 32/54] bcachefs: use the refcount instead of I_WILL_FREE|I_FREEING
* [PATCH v2 33/54] btrfs: don't check I_WILL_FREE|I_FREEING
* [PATCH v2 34/54] fs: use igrab in drop_pagecache_sb
* [PATCH v2 35/54] fs: stop checking I_FREEING in d_find_alias_rcu
* [PATCH v2 36/54] ext4: stop checking I_WILL_FREE|IFREEING in ext4_check_map_extents_env
* [PATCH v2 37/54] fs: remove I_WILL_FREE|I_FREEING from fs-writeback.c
* [PATCH v2 38/54] gfs2: remove I_WILL_FREE|I_FREEING usage
* [PATCH v2 39/54] fs: remove I_WILL_FREE|I_FREEING check from dquot.c
* [PATCH v2 40/54] notify: remove I_WILL_FREE|I_FREEING checks in fsnotify_unmount_inodes
* [PATCH v2 41/54] xfs: remove I_FREEING check
* [PATCH v2 42/54] landlock: remove I_FREEING|I_WILL_FREE check
* [PATCH v2 43/54] fs: change inode_is_dirtytime_only to use refcount
* [PATCH v2 44/54] btrfs: remove references to I_FREEING
* [PATCH v2 45/54] ext4: remove reference to I_FREEING in inode.c
* [PATCH v2 46/54] ext4: remove reference to I_FREEING in orphan.c
* [PATCH v2 47/54] pnfs: use i_count refcount to determine if the inode is going away
* [PATCH v2 48/54] fs: remove some spurious I_FREEING references in inode.c
* [PATCH v2 49/54] xfs: remove reference to I_FREEING|I_WILL_FREE
* [PATCH v2 50/54] ocfs2: do not set I_WILL_FREE
* [PATCH v2 51/54] fs: remove I_FREEING|I_WILL_FREE
* [PATCH v2 52/54] fs: remove I_REFERENCED
* [PATCH v2 53/54] fs: remove I_LRU_ISOLATING flag
* [PATCH v2 54/54] fs: add documentation explaining the reference count rules for inodes
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/ccd4eafa-7a13-48d6-93b6-f40c03262bea
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: fab1beda7597fac1cecc01707d55eadb6bbe773c
arch: amd64
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
config: https://ci.syzbot.org/builds/162c03ae-2d30-4085-ab1e-a2dd1c8403eb/config
fs/bcachefs/fs.c:350:20: error: incompatible pointer types passing 'struct bch_inode_info *' to parameter of type 'const struct inode *' [-Werror,-Wincompatible-pointer-types]
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[amir73il@gmail.com brauner@kernel.org josef@toxicpanda.com kernel-team@fb.com linux-btrfs@vger.kernel.org linux-ext4@vger.kernel.org linux-fsdevel@vger.kernel.org linux-xfs@vger.kernel.org viro@zeniv.linux.org.uk]
If the report looks fine to you, reply with:
#syz upstream
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [moderation/CI] Re: fs: rework inode reference counting
2025-08-26 20:57 [moderation/CI] Re: fs: rework inode reference counting syzbot ci
@ 2025-08-27 8:02 ` Aleksandr Nogikh
0 siblings, 0 replies; 3+ messages in thread
From: Aleksandr Nogikh @ 2025-08-27 8:02 UTC (permalink / raw)
To: syzbot ci; +Cc: syzkaller-upstream-moderation, syzbot
#syz upstream
On Tue, Aug 26, 2025 at 10:57 PM syzbot ci
<syzbot+ci41c6c35685f6a3d5@syzkaller.appspotmail.com> wrote:
>
> syzbot ci has tested the following series
>
> [v2] fs: rework inode reference counting
> https://lore.kernel.org/all/cover.1756222464.git.josef@toxicpanda.com
> * [PATCH v2 01/54] fs: make the i_state flags an enum
> * [PATCH v2 02/54] fs: add an icount_read helper
> * [PATCH v2 03/54] fs: rework iput logic
> * [PATCH v2 04/54] fs: add an i_obj_count refcount to the inode
> * [PATCH v2 05/54] fs: hold an i_obj_count reference in wait_sb_inodes
> * [PATCH v2 06/54] fs: hold an i_obj_count reference for the i_wb_list
> * [PATCH v2 07/54] fs: hold an i_obj_count reference for the i_io_list
> * [PATCH v2 08/54] fs: hold an i_obj_count reference in writeback_sb_inodes
> * [PATCH v2 09/54] fs: hold an i_obj_count reference while on the hashtable
> * [PATCH v2 10/54] fs: hold an i_obj_count reference while on the LRU list
> * [PATCH v2 11/54] fs: hold an i_obj_count reference while on the sb inode list
> * [PATCH v2 12/54] fs: stop accessing ->i_count directly in f2fs and gfs2
> * [PATCH v2 13/54] fs: hold an i_obj_count when we have an i_count reference
> * [PATCH v2 14/54] fs: add an I_LRU flag to the inode
> * [PATCH v2 15/54] fs: maintain a list of pinned inodes
> * [PATCH v2 16/54] fs: delete the inode from the LRU list on lookup
> * [PATCH v2 17/54] fs: remove the inode from the LRU list on unlink/rmdir
> * [PATCH v2 18/54] fs: change evict_inodes to use iput instead of evict directly
> * [PATCH v2 19/54] fs: hold a full ref while the inode is on a LRU
> * [PATCH v2 20/54] fs: disallow 0 reference count inodes
> * [PATCH v2 21/54] fs: make evict_inodes add to the dispose list under the i_lock
> * [PATCH v2 22/54] fs: convert i_count to refcount_t
> * [PATCH v2 23/54] fs: use refcount_inc_not_zero in igrab
> * [PATCH v2 24/54] fs: use inode_tryget in find_inode*
> * [PATCH v2 25/54] fs: update find_inode_*rcu to check the i_count count
> * [PATCH v2 26/54] fs: use igrab in insert_inode_locked
> * [PATCH v2 27/54] fs: remove I_WILL_FREE|I_FREEING check from __inode_add_lru
> * [PATCH v2 28/54] fs: remove I_WILL_FREE|I_FREEING check in inode_pin_lru_isolating
> * [PATCH v2 29/54] fs: use inode_tryget in evict_inodes
> * [PATCH v2 30/54] fs: change evict_dentries_for_decrypted_inodes to use refcount
> * [PATCH v2 31/54] block: use igrab in sync_bdevs
> * [PATCH v2 32/54] bcachefs: use the refcount instead of I_WILL_FREE|I_FREEING
> * [PATCH v2 33/54] btrfs: don't check I_WILL_FREE|I_FREEING
> * [PATCH v2 34/54] fs: use igrab in drop_pagecache_sb
> * [PATCH v2 35/54] fs: stop checking I_FREEING in d_find_alias_rcu
> * [PATCH v2 36/54] ext4: stop checking I_WILL_FREE|IFREEING in ext4_check_map_extents_env
> * [PATCH v2 37/54] fs: remove I_WILL_FREE|I_FREEING from fs-writeback.c
> * [PATCH v2 38/54] gfs2: remove I_WILL_FREE|I_FREEING usage
> * [PATCH v2 39/54] fs: remove I_WILL_FREE|I_FREEING check from dquot.c
> * [PATCH v2 40/54] notify: remove I_WILL_FREE|I_FREEING checks in fsnotify_unmount_inodes
> * [PATCH v2 41/54] xfs: remove I_FREEING check
> * [PATCH v2 42/54] landlock: remove I_FREEING|I_WILL_FREE check
> * [PATCH v2 43/54] fs: change inode_is_dirtytime_only to use refcount
> * [PATCH v2 44/54] btrfs: remove references to I_FREEING
> * [PATCH v2 45/54] ext4: remove reference to I_FREEING in inode.c
> * [PATCH v2 46/54] ext4: remove reference to I_FREEING in orphan.c
> * [PATCH v2 47/54] pnfs: use i_count refcount to determine if the inode is going away
> * [PATCH v2 48/54] fs: remove some spurious I_FREEING references in inode.c
> * [PATCH v2 49/54] xfs: remove reference to I_FREEING|I_WILL_FREE
> * [PATCH v2 50/54] ocfs2: do not set I_WILL_FREE
> * [PATCH v2 51/54] fs: remove I_FREEING|I_WILL_FREE
> * [PATCH v2 52/54] fs: remove I_REFERENCED
> * [PATCH v2 53/54] fs: remove I_LRU_ISOLATING flag
> * [PATCH v2 54/54] fs: add documentation explaining the reference count rules for inodes
>
> and found the following issue:
> kernel build error
>
> Full report is available here:
> https://ci.syzbot.org/series/ccd4eafa-7a13-48d6-93b6-f40c03262bea
>
> ***
>
> kernel build error
>
> tree: torvalds
> URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
> base: fab1beda7597fac1cecc01707d55eadb6bbe773c
> arch: amd64
> compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
> config: https://ci.syzbot.org/builds/162c03ae-2d30-4085-ab1e-a2dd1c8403eb/config
>
> fs/bcachefs/fs.c:350:20: error: incompatible pointer types passing 'struct bch_inode_info *' to parameter of type 'const struct inode *' [-Werror,-Wincompatible-pointer-types]
>
> ***
>
> If these findings have caused you to resend the series or submit a
> separate fix, please add the following tag to your commit message:
> Tested-by: syzbot@syzkaller.appspotmail.com
>
> ---
> This report is generated by a bot. It may contain errors.
> syzbot ci engineers can be reached at syzkaller@googlegroups.com.
>
> The email will later be sent to:
> [amir73il@gmail.com brauner@kernel.org josef@toxicpanda.com kernel-team@fb.com linux-btrfs@vger.kernel.org linux-ext4@vger.kernel.org linux-fsdevel@vger.kernel.org linux-xfs@vger.kernel.org viro@zeniv.linux.org.uk]
>
> If the report looks fine to you, reply with:
> #syz upstream
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-moderation+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/68ae1fb5.a70a0220.3cafd4.0001.GAE%40google.com.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-08-27 8:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-26 20:57 [moderation/CI] Re: fs: rework inode reference counting syzbot ci
2025-08-27 8:02 ` Aleksandr Nogikh
-- strict thread matches above, loose matches on Subject: below --
2025-08-21 21:08 syzbot ci
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).