From: Jiri Kosina <jkosina@suse.cz>
To: kernel test robot <lkp@intel.com>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 693/8790] drivers/hid/hid-sony.c:2159:2-14: WARNING: NULL check before some freeing functions is not needed.
Date: Wed, 4 Oct 2023 21:12:46 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.2310042112260.3534@cbobk.fhfr.pm> (raw)
In-Reply-To: <202310011609.2mhDG4jJ-lkp@intel.com>
On Sun, 1 Oct 2023, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: df964ce9ef9fea10cf131bf6bad8658fde7956f6
> commit: e1cd4004cde7c9b694bbdd8def0e02288ee58c74 [693/8790] HID: sony: Fix a potential memory leak in sony_probe()
> config: x86_64-randconfig-101-20231001 (https://download.01.org/0day-ci/archive/20231001/202310011609.2mhDG4jJ-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20231001/202310011609.2mhDG4jJ-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202310011609.2mhDG4jJ-lkp@intel.com/
>
> cocci warnings: (new ones prefixed by >>)
> >> drivers/hid/hid-sony.c:2159:2-14: WARNING: NULL check before some freeing functions is not needed.
Now fixed in hid.git#for-6.6/upstream-fixes with 287f69f3f9939.
--
Jiri Kosina
Director, SUSE Labs Core
prev parent reply other threads:[~2023-10-04 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 9:03 kernel test robot
2023-10-04 19:12 ` Jiri Kosina [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=nycvar.YFH.7.76.2310042112260.3534@cbobk.fhfr.pm \
--to=jkosina@suse.cz \
--cc=christophe.jaillet@wanadoo.fr \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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