[Cluster-devel] dlm build failure (was: Re: linux-next: Tree for Nov 22)
On Tue, Nov 22, 2022 at 8:40 AM Stephen Rothwell wrote:
> Merging dlm/next (dbb751ffab0b fs: dlm: parallelize lowcomms socket handling)
nore...@ellerman.id.au reported a build failure for e.g. m68k/defconfig[1]:
ERROR: modpost: "lockdep_is_held" [fs/dlm/dlm.ko] undefined!
which I have bisected to this commit. The corresponding patch does not seem
to have been posted for public review to any mailing list archived by lore.
[1] http://kisskb.ellerman.id.au/kisskb/buildresult/14835766/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: [Cluster-devel] [PATCH] filelock: move file locking definitions to separate header file
On Tue, 2022-11-22 at 03:51 +, Matthew Wilcox wrote: > On Sun, Nov 20, 2022 at 03:59:57PM -0500, Jeff Layton wrote: > > Move the file locking definitions to a new header file, and add the > > appropriate #include directives to the source files that need them. By > > doing this we trim down fs.h a bit and limit the amount of rebuilding > > that has to be done when we make changes to the file locking APIs. > > I'm in favour of this in general, but I think there's a few implicit > includes. Can you create a test.c that only #include > and see if there's anything missing? > > > + wait_queue_head_t fl_wait; > > + struct file *fl_file; > > These two seem undefined at this point. > > > + struct fasync_struct * fl_fasync; /* for lease break notifications */ > > Likewise. > Yeah, there is quite a bit missing. I think I'll have to add this at the head of filelock.h: #include ...as we need several definitions from fs.h for this header. -- Jeff Layton
Re: [Cluster-devel] [PATCH v1 2/3] Treewide: Stop corrupting socket's task_frag
On 11/21/22 15:01, Benjamin Coddington wrote: On 21 Nov 2022, at 16:43, Shuah Khan wrote: On 11/21/22 14:40, Shuah Khan wrote: On 11/21/22 07:34, Benjamin Coddington wrote: On 21 Nov 2022, at 8:56, David Howells wrote: Benjamin Coddington wrote: Since moving to memalloc_nofs_save/restore, SUNRPC has stopped setting the GFP_NOIO flag on sk_allocation which the networking system uses to decide when it is safe to use current->task_frag. Um, what's task_frag? Its a per-task page_frag used to coalesce small writes for networking -- see: 5640f7685831 net: use a per task frag allocator Ben I am not seeing this in the mainline. Where can find this commit? Okay. I see this commit in the mainline. However, I don't see the sk_use_task_frag in mainline. sk_use_task_frag is in patch 1/3 in this posting. https://lore.kernel.org/netdev/26d98c8f-372b-b9c8-c29f-096cddaff...@linuxfoundation.org/T/#m3271959c4cf8dcff1c0c6ba023b2b3821d9e7e99 Aha. I don't have 1/3 in my Inbox - I think it would make sense to cc people on the first patch so we can understand the premise for the change. thanks, -- Shuah
Re: [Cluster-devel] [PATCH v1 2/3] Treewide: Stop corrupting socket's task_frag
On 11/21/22 14:40, Shuah Khan wrote: On 11/21/22 07:34, Benjamin Coddington wrote: On 21 Nov 2022, at 8:56, David Howells wrote: Benjamin Coddington wrote: Since moving to memalloc_nofs_save/restore, SUNRPC has stopped setting the GFP_NOIO flag on sk_allocation which the networking system uses to decide when it is safe to use current->task_frag. Um, what's task_frag? Its a per-task page_frag used to coalesce small writes for networking -- see: 5640f7685831 net: use a per task frag allocator Ben I am not seeing this in the mainline. Where can find this commit? Okay. I see this commit in the mainline. However, I don't see the sk_use_task_frag in mainline. thanks, -- Shuah
Re: [Cluster-devel] [PATCH v1 2/3] Treewide: Stop corrupting socket's task_frag
On 11/21/22 07:34, Benjamin Coddington wrote: On 21 Nov 2022, at 8:56, David Howells wrote: Benjamin Coddington wrote: Since moving to memalloc_nofs_save/restore, SUNRPC has stopped setting the GFP_NOIO flag on sk_allocation which the networking system uses to decide when it is safe to use current->task_frag. Um, what's task_frag? Its a per-task page_frag used to coalesce small writes for networking -- see: 5640f7685831 net: use a per task frag allocator Ben I am not seeing this in the mainline. Where can find this commit? thanks, -- Shuah
Re: [Cluster-devel] [PATCH] filelock: move file locking definitions to separate header file
On Tue, 2022-11-22 at 09:51 +0800, Joseph Qi wrote: > Hi, > > On 11/21/22 4:59 AM, Jeff Layton wrote: > > The file locking definitions have lived in fs.h since the dawn of time, > > but they are only used by a small subset of the source files that > > include it. > > > > Move the file locking definitions to a new header file, and add the > > appropriate #include directives to the source files that need them. By > > doing this we trim down fs.h a bit and limit the amount of rebuilding > > that has to be done when we make changes to the file locking APIs. > > > > Signed-off-by: Jeff Layton > > --- > > fs/9p/vfs_file.c | 1 + > > fs/afs/internal.h | 1 + > > fs/attr.c | 1 + > > fs/ceph/locks.c | 1 + > > fs/cifs/cifsfs.c | 1 + > > fs/cifs/cifsglob.h| 1 + > > fs/cifs/cifssmb.c | 1 + > > fs/cifs/file.c| 1 + > > fs/cifs/smb2file.c| 1 + > > fs/dlm/plock.c| 1 + > > fs/fcntl.c| 1 + > > fs/file_table.c | 1 + > > fs/fuse/file.c| 1 + > > fs/gfs2/file.c| 1 + > > fs/inode.c| 1 + > > fs/ksmbd/smb2pdu.c| 1 + > > fs/ksmbd/vfs.c| 1 + > > fs/ksmbd/vfs_cache.c | 1 + > > fs/lockd/clntproc.c | 1 + > > fs/lockd/netns.h | 1 + > > fs/locks.c| 1 + > > fs/namei.c| 1 + > > fs/nfs/nfs4_fs.h | 1 + > > fs/nfs_common/grace.c | 1 + > > fs/nfsd/netns.h | 1 + > > fs/ocfs2/locks.c | 1 + > > fs/ocfs2/stack_user.c | 1 + > > Seems it misses the related changes in: > fs/ocfs2/stackglue.c > I was able to build ocfs2.ko just fine without any changes to stackglue.c. What problem do you see here? Thanks, -- Jeff Layton
Re: [Cluster-devel] [PATCH] filelock: move file locking definitions to separate header file
On 11/22/22 8:20 PM, Jeff Layton wrote: > On Tue, 2022-11-22 at 09:51 +0800, Joseph Qi wrote: >> Hi, >> >> On 11/21/22 4:59 AM, Jeff Layton wrote: >>> The file locking definitions have lived in fs.h since the dawn of time, >>> but they are only used by a small subset of the source files that >>> include it. >>> >>> Move the file locking definitions to a new header file, and add the >>> appropriate #include directives to the source files that need them. By >>> doing this we trim down fs.h a bit and limit the amount of rebuilding >>> that has to be done when we make changes to the file locking APIs. >>> >>> Signed-off-by: Jeff Layton >>> --- >>> fs/9p/vfs_file.c | 1 + >>> fs/afs/internal.h | 1 + >>> fs/attr.c | 1 + >>> fs/ceph/locks.c | 1 + >>> fs/cifs/cifsfs.c | 1 + >>> fs/cifs/cifsglob.h| 1 + >>> fs/cifs/cifssmb.c | 1 + >>> fs/cifs/file.c| 1 + >>> fs/cifs/smb2file.c| 1 + >>> fs/dlm/plock.c| 1 + >>> fs/fcntl.c| 1 + >>> fs/file_table.c | 1 + >>> fs/fuse/file.c| 1 + >>> fs/gfs2/file.c| 1 + >>> fs/inode.c| 1 + >>> fs/ksmbd/smb2pdu.c| 1 + >>> fs/ksmbd/vfs.c| 1 + >>> fs/ksmbd/vfs_cache.c | 1 + >>> fs/lockd/clntproc.c | 1 + >>> fs/lockd/netns.h | 1 + >>> fs/locks.c| 1 + >>> fs/namei.c| 1 + >>> fs/nfs/nfs4_fs.h | 1 + >>> fs/nfs_common/grace.c | 1 + >>> fs/nfsd/netns.h | 1 + >>> fs/ocfs2/locks.c | 1 + >>> fs/ocfs2/stack_user.c | 1 + >> >> Seems it misses the related changes in: >> fs/ocfs2/stackglue.c >> > > I was able to build ocfs2.ko just fine without any changes to > stackglue.c. What problem do you see here? > Okay, that's because there is prototype declaration in fs/ocfs2/stackglue.h, and it seems has no real effect in current version. So it looks good to me. For ocfs2 part, Acked-by: Joseph Qi
Re: [Cluster-devel] [PATCH v1 2/3] Treewide: Stop corrupting socket's task_frag
On 21 Nov 2022, at 17:32, Shuah Khan wrote: > On 11/21/22 15:01, Benjamin Coddington wrote: >> On 21 Nov 2022, at 16:43, Shuah Khan wrote: >> >>> On 11/21/22 14:40, Shuah Khan wrote: On 11/21/22 07:34, Benjamin Coddington wrote: > On 21 Nov 2022, at 8:56, David Howells wrote: > >> Benjamin Coddington wrote: >> >>> Since moving to memalloc_nofs_save/restore, SUNRPC has stopped setting >>> the >>> GFP_NOIO flag on sk_allocation which the networking system uses to >>> decide >>> when it is safe to use current->task_frag. >> >> Um, what's task_frag? > > Its a per-task page_frag used to coalesce small writes for networking -- > see: > > 5640f7685831 net: use a per task frag allocator > > Ben > > I am not seeing this in the mainline. Where can find this commit? >>> >>> Okay. I see this commit in the mainline. However, I don't see the >>> sk_use_task_frag in mainline. >> >> sk_use_task_frag is in patch 1/3 in this posting. >> >> https://lore.kernel.org/netdev/26d98c8f-372b-b9c8-c29f-096cddaff...@linuxfoundation.org/T/#m3271959c4cf8dcff1c0c6ba023b2b3821d9e7e99 >> > > Aha. I don't have 1/3 in my Inbox - I think it would make > sense to cc people on the first patch so we can understand > the premise for the change. Yeah, I can do that if it goes to another version, I was just trying to be considerate of all the noise this sort of posting generates. Ben
[Cluster-devel] [PATCH dlm/next] fs: dlm: fix building without lockdep
This patch uses assert_spin_locked() instead of lockdep_is_held()
where it's available to use because lockdep_is_held() is only available
if CONFIG_LOCKDEP is set.
In other cases like lockdep_sock_is_held() we surround it by a
CONFIG_LOCKDEP idef.
Fixes: dbb751ffab0b ("fs: dlm: parallelize lowcomms socket handling")
Reported-by: kernel test robot
Signed-off-by: Alexander Aring
---
fs/dlm/lowcomms.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
index 799d1c36eabf..8b80ca0cd65f 100644
--- a/fs/dlm/lowcomms.c
+++ b/fs/dlm/lowcomms.c
@@ -208,7 +208,7 @@ bool dlm_lowcomms_is_running(void)
static void lowcomms_queue_swork(struct connection *con)
{
- WARN_ON_ONCE(!lockdep_is_held(&con->writequeue_lock));
+ assert_spin_locked(&con->writequeue_lock);
if (!test_bit(CF_IO_STOP, &con->flags) &&
!test_bit(CF_APP_LIMITED, &con->flags) &&
@@ -218,7 +218,9 @@ static void lowcomms_queue_swork(struct connection *con)
static void lowcomms_queue_rwork(struct connection *con)
{
+#ifdef CONFIG_LOCKDEP
WARN_ON_ONCE(!lockdep_sock_is_held(con->sock->sk));
+#endif
if (!test_bit(CF_IO_STOP, &con->flags) &&
!test_and_set_bit(CF_RECV_PENDING, &con->flags))
@@ -618,7 +620,9 @@ static void lowcomms_error_report(struct sock *sk)
static void restore_callbacks(struct sock *sk)
{
+#ifdef CONFIG_LOCKDEP
WARN_ON_ONCE(!lockdep_sock_is_held(sk));
+#endif
sk->sk_user_data = NULL;
sk->sk_data_ready = listen_sock.sk_data_ready;
--
2.31.1
Re: [Cluster-devel] [syzbot] kernel BUG in gfs2_glock_nq (2)
syzbot has found a reproducer for the following issue on: HEAD commit:eb7081409f94 Linux 6.1-rc6 git tree: upstream console+strace: https://syzkaller.appspot.com/x/log.txt?x=15d40efd88 kernel config: https://syzkaller.appspot.com/x/.config?x=8cdf448d3b35234 dashboard link: https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80 compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156d55fd88 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1494607588 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/4a019f55c517/disk-eb708140.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/eb36e890aa8b/vmlinux-eb708140.xz kernel image: https://storage.googleapis.com/syzbot-assets/feee2c23ec64/bzImage-eb708140.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/595931ddaae3/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+70f4e455dee59ab40...@syzkaller.appspotmail.com gfs2: fsid=syz:syz.0: new: gfs2_quota_sync+0x3da/0x8b0 fs/gfs2/quota.c:1318 gfs2: fsid=syz:syz.0: pid: 3642 gfs2: fsid=syz:syz.0: lock type: 8 req lock state : 1 gfs2: fsid=syz:syz.0: G: s:EX n:8/1 f:qb t:EX d:EX/0 a:0 v:0 r:5 m:20 p:0 gfs2: fsid=syz:syz.0: H: s:EX f:cH e:0 p:3642 [syz-executor297] gfs2_quota_sync+0x3da/0x8b0 fs/gfs2/quota.c:1318 [ cut here ] kernel BUG at fs/gfs2/glock.c:1560! invalid opcode: [#1] PREEMPT SMP KASAN CPU: 0 PID: 3642 Comm: syz-executor297 Not tainted 6.1.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 RIP: 0010:add_to_queue fs/gfs2/glock.c:1560 [inline] RIP: 0010:gfs2_glock_nq+0x1661/0x1890 fs/gfs2/glock.c:1585 Code: 0f b7 4d 00 48 c7 c7 00 42 3e 8b 48 8b 74 24 20 89 da 31 c0 e8 9c bf da 06 31 ff 48 8b 74 24 28 ba 01 00 00 00 e8 6f 7b ff ff <0f> 0b 89 d9 80 e1 07 fe c1 38 c1 0f 8c 94 ee ff ff 48 89 df e8 06 RSP: 0018:c90003baf898 EFLAGS: 00010246 RAX: 366be81aeeac0c00 RBX: 0008 RCX: 88807253d7c0 RDX: RSI: 0001 RDI: RBP: 888027cb365a R08: 83b90f42 R09: fbfff1d2f2de R10: fbfff1d2f2de R11: 11d2f2dd R12: 888027cb3638 R13: 888073045340 R14: 888027cb3630 R15: 111004f966c3 FS: () GS:8880b980() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 562ec3072000 CR3: 714f CR4: 003506f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: gfs2_glock_nq_init fs/gfs2/glock.h:264 [inline] do_sync+0x3b1/0xc80 fs/gfs2/quota.c:910 gfs2_quota_sync+0x3da/0x8b0 fs/gfs2/quota.c:1318 gfs2_sync_fs+0x49/0xb0 fs/gfs2/super.c:643 sync_filesystem+0xe8/0x220 fs/sync.c:56 generic_shutdown_super+0x6b/0x310 fs/super.c:474 kill_block_super+0x79/0xd0 fs/super.c:1428 deactivate_locked_super+0xa7/0xf0 fs/super.c:332 cleanup_mnt+0x494/0x520 fs/namespace.c:1186 task_work_run+0x243/0x300 kernel/task_work.c:179 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x664/0x2070 kernel/exit.c:820 do_group_exit+0x1fd/0x2b0 kernel/exit.c:950 __do_sys_exit_group kernel/exit.c:961 [inline] __se_sys_exit_group kernel/exit.c:959 [inline] __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:959 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f9613abc989 Code: Unable to access opcode bytes at 0x7f9613abc95f. RSP: 002b:7ffe22a048c8 EFLAGS: 0246 ORIG_RAX: 00e7 RAX: ffda RBX: 7f9613b6d330 RCX: 7f9613abc989 RDX: 003c RSI: 00e7 RDI: 0001 RBP: 0001 R08: ffc0 R09: 0003b2d3 R10: R11: 0246 R12: 7f9613b6d330 R13: 0001 R14: R15: 0001 Modules linked in: ---[ end trace ]--- RIP: 0010:add_to_queue fs/gfs2/glock.c:1560 [inline] RIP: 0010:gfs2_glock_nq+0x1661/0x1890 fs/gfs2/glock.c:1585 Code: 0f b7 4d 00 48 c7 c7 00 42 3e 8b 48 8b 74 24 20 89 da 31 c0 e8 9c bf da 06 31 ff 48 8b 74 24 28 ba 01 00 00 00 e8 6f 7b ff ff <0f> 0b 89 d9 80 e1 07 fe c1 38 c1 0f 8c 94 ee ff ff 48 89 df e8 06 RSP: 0018:c90003baf898 EFLAGS: 00010246 RAX: 366be81aeeac0c00 RBX: 0008 RCX: 88807253d7c0 RDX: RSI: 0001 RDI: RBP: 888027cb365a R08: 83b90f42 R09: fbfff1d2f2de R10: fbfff1d2f2de R11: 11d2f2dd R12: 888027cb3638 R13: 888073045340 R14: 888027cb3630 R15: 111004f966c3 FS: () GS:8880b98
[Cluster-devel] [linux-next:master] BUILD REGRESSION 771a207d1ee9f38da8c0cee1412228f18b900bac
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 771a207d1ee9f38da8c0cee1412228f18b900bac Add linux-next specific files for 20221122 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202211130053.np70vidn-...@intel.com https://lore.kernel.org/oe-kbuild-all/202211211917.ylicunmb-...@intel.com https://lore.kernel.org/oe-kbuild-all/202211221848.n0wn2gk3-...@intel.com https://lore.kernel.org/oe-kbuild-all/202211221932.a1a12ylh-...@intel.com https://lore.kernel.org/oe-kbuild-all/202211222131.h2kt55xh-...@intel.com https://lore.kernel.org/oe-kbuild-all/202211222348.riebqcjq-...@intel.com Error/Warning: (recently discovered and may have been fixed) ERROR: modpost: "__ld_r13_to_r22" [lib/zstd/zstd_decompress.ko] undefined! ERROR: modpost: "devm_ioremap_resource" [drivers/dma/qcom/hdma.ko] undefined! ERROR: modpost: "lockdep_is_held" [fs/dlm/dlm.ko] undefined! arch/arm/mach-s3c/devs.c:32:10: fatal error: linux/platform_data/dma-s3c24xx.h: No such file or directory drivers/clk/clk.c:1022:5: error: redefinition of 'clk_prepare' drivers/clk/clk.c:1268:6: error: redefinition of 'clk_is_enabled_when_prepared' drivers/clk/clk.c:941:6: error: redefinition of 'clk_unprepare' drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4968: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:5075:24: warning: implicit conversion from 'enum ' to 'enum dc_status' [-Wenum-conversion] drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dcn201/irq_service_dcn201.c:139:43: warning: unused variable 'dmub_outbox_irq_info_funcs' [-Wunused-const-variable] drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dcn201/irq_service_dcn201.c:40:20: warning: no previous prototype for 'to_dal_irq_source_dcn201' [-Wmissing-prototypes] drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dcn201/irq_service_dcn201.c:40:20: warning: no previous prototype for function 'to_dal_irq_source_dcn201' [-Wmissing-prototypes] drivers/gpu/drm/nouveau/nvkm/engine/fifo/gf100.c:451:1: warning: no previous prototype for 'gf100_fifo_nonstall_block' [-Wmissing-prototypes] drivers/gpu/drm/nouveau/nvkm/engine/fifo/gf100.c:451:1: warning: no previous prototype for function 'gf100_fifo_nonstall_block' [-Wmissing-prototypes] drivers/gpu/drm/nouveau/nvkm/engine/fifo/runl.c:34:1: warning: no previous prototype for 'nvkm_engn_cgrp_get' [-Wmissing-prototypes] drivers/gpu/drm/nouveau/nvkm/engine/fifo/runl.c:34:1: warning: no previous prototype for function 'nvkm_engn_cgrp_get' [-Wmissing-prototypes] drivers/gpu/drm/nouveau/nvkm/engine/gr/tu102.c:210:1: warning: no previous prototype for 'tu102_gr_load' [-Wmissing-prototypes] drivers/gpu/drm/nouveau/nvkm/engine/gr/tu102.c:210:1: warning: no previous prototype for function 'tu102_gr_load' [-Wmissing-prototypes] drivers/gpu/drm/nouveau/nvkm/nvfw/acr.c:49:1: warning: no previous prototype for 'wpr_generic_header_dump' [-Wmissing-prototypes] drivers/gpu/drm/nouveau/nvkm/nvfw/acr.c:49:1: warning: no previous prototype for function 'wpr_generic_header_dump' [-Wmissing-prototypes] drivers/gpu/drm/nouveau/nvkm/subdev/acr/lsfw.c:221:21: warning: variable 'loc' set but not used [-Wunused-but-set-variable] fs/dlm/lowcomms.c:623: undefined reference to `lockdep_is_held' include/net/sock.h:1713: undefined reference to `lockdep_is_held' ld.lld: error: undefined symbol: devm_drm_of_get_bridge ld.lld: error: undefined symbol: drm_atomic_get_new_connector_for_encoder ld.lld: error: undefined symbol: drm_atomic_helper_bridge_destroy_state ld.lld: error: undefined symbol: drm_atomic_helper_bridge_duplicate_state ld.lld: error: undefined symbol: drm_atomic_helper_bridge_reset ld.lld: error: undefined symbol: drm_bridge_add ld.lld: error: undefined symbol: drm_bridge_attach ld.lld: error: undefined symbol: drm_bridge_remove ld.lld: error: undefined symbol: drm_of_get_data_lanes_count_ep ld.lld: error: undefined symbol: lockdep_is_held microblaze-linux-ld: (.text+0x158): undefined reference to `drm_bridge_add' microblaze-linux-ld: drivers/gpu/drm/rcar-du/rzg2l_mipi_dsi.o:(.rodata+0x3b4): undefined reference to `drm_atomic_helper_bridge_duplicate_state' microblaze-linux-ld: drivers/gpu/drm/rcar-du/rzg2l_mipi_dsi.o:(.rodata+0x3b8): undefined reference to `drm_atomic_helper_bridge_destroy_state' microblaze-linux-ld: drivers/gpu/drm/rcar-du/rzg2l_mipi_dsi.o:(.rodata+0x3c8): undefined reference to `drm_atomic_helper_bridge_reset' Unverified Error/Warning (likely false positive, please contact us if interested): drivers/gpu/drm/nouveau/nvkm/falcon/base.c:47:23: warning: use of uninitialized value '' [CWE-457] [-Wa
