From: Dan Carpenter <dan.carpenter@oracle.com>
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: smatch@vger.kernel.org
Subject: Re: [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev
Date: Wed, 4 Aug 2021 17:55:57 +0300 [thread overview]
Message-ID: <20210804145557.GH22532@kadam> (raw)
In-Reply-To: <638a2d48-59d3-30c3-8ef4-56d9f0d3f56a@gmail.com>
On Wed, Aug 04, 2021 at 05:44:09PM +0300, Pavel Skripkin wrote:
> On 8/4/21 5:35 PM, Dan Carpenter wrote:
> > Pushed!
> >
> > This finds two bugs in my allmodconfig. They're both real bugs.
> >
> > drivers/net/ethernet/freescale/fec_main.c:3994 fec_drv_remove() error: Using fep after free_{netdev,candev}(ndev);
> > drivers/net/ethernet/freescale/fec_main.c:3995 fec_drv_remove() error: Using fep after free_{netdev,candev}(ndev);
> > drivers/net/ethernet/neterion/vxge/vxge-main.c:3518 vxge_device_unregister() error: Using vdev after free_{netdev,candev}(dev);
> > drivers/net/ethernet/neterion/vxge/vxge-main.c:3518 vxge_device_unregister() error: Using vdev after free_{netdev,candev}(dev);
> > drivers/net/ethernet/neterion/vxge/vxge-main.c:3520 vxge_device_unregister() error: Using vdev after free_{netdev,candev}(dev);
> > drivers/net/ethernet/neterion/vxge/vxge-main.c:3520 vxge_device_unregister() error: Using vdev after free_{netdev,candev}(dev);
> >
>
> I can send patches to fix these errors with Reported-by tag, or You will
> take care of it?
Yes, please send the fixes. These are your discovery. You get first
dibs. ;)
regards,
dan carpenter
prev parent reply other threads:[~2021-08-04 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 21:00 [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev Pavel Skripkin
2021-08-03 15:08 ` Dan Carpenter
2021-08-03 16:03 ` Pavel Skripkin
2021-08-04 7:05 ` Dan Carpenter
2021-08-04 14:35 ` Dan Carpenter
2021-08-04 14:40 ` Pavel Skripkin
2021-08-04 14:44 ` Pavel Skripkin
2021-08-04 14:55 ` Dan Carpenter [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=20210804145557.GH22532@kadam \
--to=dan.carpenter@oracle.com \
--cc=paskripkin@gmail.com \
--cc=smatch@vger.kernel.org \
/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