From: Yves-Alexis Perez <corsac@corsac.net>
To: Bernd Eckstein <3erndeckstein@gmail.com>, davem@davemloft.net
Cc: linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, 3ernd.Eckstein@gmail.com,
Oliver Zweigle <Oliver.Zweigle@faro.com>
Subject: Re: [PATCH] usbnet: ipheth: fix potential recvmsg bug and recvmsg bug 2
Date: Fri, 23 Nov 2018 14:07:18 +0100 [thread overview]
Message-ID: <df9bc91da52405f4cf1e75e2530151317068c46f.camel@corsac.net> (raw)
In-Reply-To: <1542977486-15363-1-git-send-email-3ernd.Eckstein@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Fri, 2018-11-23 at 13:51 +0100, Bernd Eckstein wrote:
> This causes the following problems:
> - double free of the skb or potential memory leak
> - in dmesg: 'recvmsg bug' and 'recvmsg bug 2' and eventually
> general protection fault
For what it's worth, Bernd contacted me because it looks like this was the
cause of https://lore.kernel.org/lkml/20180605085450.GA3506@scapa.corsac.net/
I wanted to try Bernd patch, unfortunately I wasn't able to reproduce the
freezes on more recent kernels, so right now I can't add a Tested-By, but I'd
be happy to be kept on CC.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlv3+4YACgkQ3rYcyPpX
RFuuoQgAhJHvzpl1yr7ZM215DviNj8Q/n7WpiWSk6ik5Ts8n4qsgIRcXojhEPfkw
KAmpJ7G1zRgxRtZayiKLUl7RE3uWNOjTph3pzztBmMI+P7C/R4pVdZeRlandGsju
YH6G32u+BB55tJw/TYrahlG3Ni0HNDoL+QfgJJno6/dr9V+YFr+opTCuDchaBHeJ
acVsogUkyclvAutHt3UMjiDvVB12mW6IFz997y1Fv3JMT9HTQrDT9VdMUSr2WC5s
rb9ONoim1ADDgTBN10mbPWZ80aooR8GtNEGpFa2EL0vPdNVlqyZqV46hYbLuZZ42
tMF3AD6hrQqxitCS3QGJpWjFFscFMA==
=OkrF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-11-23 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 12:51 [PATCH] usbnet: ipheth: fix potential recvmsg bug and recvmsg bug 2 Bernd Eckstein
2018-11-23 13:07 ` Yves-Alexis Perez [this message]
2018-11-27 22:59 ` David Miller
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=df9bc91da52405f4cf1e75e2530151317068c46f.camel@corsac.net \
--to=corsac@corsac.net \
--cc=3ernd.Eckstein@gmail.com \
--cc=3erndeckstein@gmail.com \
--cc=Oliver.Zweigle@faro.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).