From: Simon Horman <horms@kernel.org>
To: Deepak Sharma <deepak.sharma.472935@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, pwn9uin@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+07b635b9c111c566af8b@syzkaller.appspotmail.com
Subject: Re: [PATCH] Fix the cleanup on alloc_mpc failure in atm_mpoa_mpoad_attach
Date: Wed, 24 Sep 2025 19:41:15 +0100 [thread overview]
Message-ID: <20250924184115.GS836419@horms.kernel.org> (raw)
In-Reply-To: <20250923132427.74242-1-deepak.sharma.472935@gmail.com>
On Tue, Sep 23, 2025 at 06:54:27PM +0530, Deepak Sharma wrote:
> Syzbot reported a warning at `add_timer`, which is called from the
> `atm_mpoa_mpoad_attach` function
>
> The reason for this warning is that in the allocation failure by `alloc_mpc`,
> there is lack of proper cleanup. And in the event that ATMMPC_CTRL ioctl is
> called on to again, it will lead to the attempt of starting an already
> started timer from the previous ioctl call
>
> Do a `timer_delete` before returning from the `alloc_mpc` failure
>
> Reported-by: syzbot+07b635b9c111c566af8b@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=07b635b9c111c566af8b
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Deepak Sharma <deepak.sharma.472935@gmail.com>
> ---
> net/atm/mpc.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/atm/mpc.c b/net/atm/mpc.c
> index f6b447bba329..cd3295c3c480 100644
> --- a/net/atm/mpc.c
> +++ b/net/atm/mpc.c
> @@ -814,7 +814,10 @@ static int atm_mpoa_mpoad_attach(struct atm_vcc *vcc, int arg)
> dprintk("allocating new mpc for itf %d\n", arg);
> mpc = alloc_mpc();
> if (mpc == NULL)
> + {
> + timer_delete(&mpc_timer);
> return -ENOMEM;
> + }
> mpc->dev_num = arg;
> mpc->dev = find_lec_by_itfnum(arg);
> /* NULL if there was no lec */
Hi Deepak.
I have a few questions about this.
1. Is timer_delete() sufficient, or is timer_delete_sync() needed
to avoid the timer being rearmed?
2. If timer_delete_sync() is needed here, then it is probably
also needed a few lines above, in place of an existing call to
timer_delete().
3. Is timer_delete()/timer_delete_sync() also needed for the error condition a
few lines below the hunk above? That code looks like this:
if (mpc->mpoad_vcc) {
pr_info("mpoad is already present for itf %d\n", arg);
return -EADDRINUSE;
}
Also, this patch is probably for net. So, for reference, it should
be targeted at that tree like this:
Subject: [PATCH net] ...
And the patch subject should have a prefix. Looking at git history, "atm:"
seems appropriate.
Subject: [PATCH net] atm: ...
next prev parent reply other threads:[~2025-09-24 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 13:24 [PATCH] Fix the cleanup on alloc_mpc failure in atm_mpoa_mpoad_attach Deepak Sharma
2025-09-24 18:41 ` Simon Horman [this message]
2025-09-24 18:44 ` Simon Horman
2025-09-24 23:45 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2025-09-23 13:28 Deepak Sharma
2025-09-25 20:40 Deepak Sharma
2025-09-28 15:26 ` David Hunter
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=20250924184115.GS836419@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=deepak.sharma.472935@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pwn9uin@gmail.com \
--cc=syzbot+07b635b9c111c566af8b@syzkaller.appspotmail.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.