mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Jiangshan Yi <yijiangshan@kylinos.cn>
Cc: <lkp@intel.com>, <13667453960@163.com>, <arnd@arndb.de>,
	<gregkh@linuxfoundation.org>, <kees@kernel.org>,
	<linux-kernel@vger.kernel.org>, <oe-kbuild-all@lists.linux.dev>
Subject: Re: Re: [PATCH] lkdtm/core: fix resource leaks on module init error path
Date: Tue, 11 Aug 2026 13:12:23 +0800	[thread overview]
Message-ID: <anqvN8zNo+IferI2@rli9-mobl> (raw)
In-Reply-To: <20260810014815.76401-1-yijiangshan@kylinos.cn>

On Mon, Aug 10, 2026 at 09:48:15AM +0800, Jiangshan Yi wrote:
> Hi,
> 
> Thanks for the build test report and for catching these section mismatch
> warnings:
> 
> > All warnings (new ones prefixed by >>, old ones prefixed by <<):
> >
> > WARNING: modpost: "saved_config" [vmlinux] is COMMON symbol
> > >> WARNING: modpost: vmlinux: section mismatch in reference: lkdtm_module_init+0x1ec (section: .init.text) -> lkdtm_heap_exit (section: .exit.text)
> > WARNING: modpost: vmlinux: section mismatch in reference: lkdtm_module_init+0x1f0 (section: .init.text) -> lkdtm_heap_exit (section: .exit.text)
> > >> WARNING: modpost: vmlinux: section mismatch in reference: lkdtm_module_init+0x1fc (section: .init.text) -> lkdtm_usercopy_exit (section: .exit.text)
> > WARNING: modpost: vmlinux: section mismatch in reference: lkdtm_module_init+0x200 (section: .init.text) -> lkdtm_usercopy_exit (section: .exit.text)
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
> 
> These warnings have already been addressed in the v2 of this patch,
> posted at:
> 
> https://lore.kernel.org/all/20260730154911.3164527-1-yijiangshan@kylinos.cn/

Sorry about the noise, the bot doesn't recognize the v2 correctly, we will
fix it to avoid false positive.

> 
> In v2, the error-handling path in lkdtm_module_init() no longer
> references the .exit.text cleanup helpers (lkdtm_heap_exit,
> lkdtm_usercopy_exit), which resolves the section mismatch reported
> by modpost.
> 
> Since the fix is part of a new version of the same patch rather than a
> separate commit, I haven't added the Reported-by / Closes tags to
> that version. However, your report was very helpful in confirming the
> issue — thank you again for the testing.
> 
> Best regards,
> Jiangshan Yi
> 

      reply	other threads:[~2026-08-11  5:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 15:14 Jiangshan Yi
2026-08-05  1:57 ` kernel test robot
2026-08-05  2:27   ` Jiangshan Yi
2026-08-05  7:11 ` kernel test robot
2026-08-10  1:48   ` Jiangshan Yi
2026-08-11  5:12     ` Philip Li [this message]

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=anqvN8zNo+IferI2@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=13667453960@163.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yijiangshan@kylinos.cn \
    /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

all inboxes | Powered by JetHome®