All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>
To: syzbot <syzbot+afc686a471d70896c5d9@syzkaller.appspotmail.com>
Cc: dwlsalmeida@gmail.com, linux-kernel@vger.kernel.org,
	 linux-media@vger.kernel.org, mchehab@kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] media: dvb-core: fix memory leak in dvb_dmxdev_add_pid() on start failure
Date: Wed, 13 May 2026 11:05:35 +0200	[thread overview]
Message-ID: <agQ-Pq7o6LXwxUEg@gmail.com> (raw)
In-Reply-To: <advi5yTDwVkRTpV5@gmail.com>

On Sun, Apr 12, 2026 at 08:25:51PM +0200, Jose A. Perez de Azpillaga wrote:
> When dvb_dmxdev_add_pid() adds a new dmxdev_feed to the filter's ts list
> and then dvb_dmxdev_start_feed() fails, the function returns the error
> code but leaves the orphaned feed entry in the list without cleaning up.
>
> Fix this by removing the orphaned feed from the list and freeing it when
> dvb_dmxdev_start_feed() fails in dvb_dmxdev_add_pid().
>
> Fixes: 1cb662a31449 ("V4L/DVB (12275): Add two new ioctls: DMX_ADD_PID and DMX_REMOVE_PID")
> Reported-by: syzbot+afc686a471d70896c5d9@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=afc686a471d70896c5d9
> Tested-by: syzbot+afc686a471d70896c5d9@syzkaller.appspotmail.com
> Signed-off-by: Jose A. Perez de Azpillaga <azpijr@gmail.com>

hi,

just a gentle ping for this patch. is there anything else needed from my
side?

thanks

--
jose a. p-a

      reply	other threads:[~2026-05-13  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 20:04 [syzbot] [media?] memory leak in vidtv_psi_short_event_desc_init syzbot
2026-04-12 13:11 ` Jose A. Perez de Azpillaga
2026-04-12 14:55   ` syzbot
2026-04-12 16:20 ` Jose A. Perez de Azpillaga
2026-04-12 17:13   ` syzbot
2026-04-12 18:25 ` [PATCH] media: dvb-core: fix memory leak in dvb_dmxdev_add_pid() on start failure Jose A. Perez de Azpillaga
2026-05-13  9:05   ` Jose A. Perez de Azpillaga [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=agQ-Pq7o6LXwxUEg@gmail.com \
    --to=azpijr@gmail.com \
    --cc=dwlsalmeida@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=syzbot+afc686a471d70896c5d9@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.