From: dyslexicatheist <dyslexicatheist@protonmail.com>
To: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: invalid read in
Date: Mon, 03 Feb 2020 17:49:36 +0000 [thread overview]
Message-ID: <s7HX6aItJNJ0k3vJDOdNMEIR5DZxNsav0EwjPqFGroEYHSRmMrGoNy6SX_gHXvSatbsTt1yNihtxUXK_ARVqtWmAsDhmD5fudDnu4mA8Tro=@protonmail.com> (raw)
In-Reply-To: <20200203173003.GF20229@orbyte.nwl.cc>
On Monday, February 3, 2020 5:30 PM, Phil Sutter <phil@nwl.cc> wrote:
> > thanks for your help Phil. I have just tried this but unfortunately it didn't change the outcome. Also tried other variations such as memset'ing both &u and the ¶ms struct, but nada.
>
> Maybe you need to apply the same to __build_send_cfg_msg() as well?
thanks, I just tried this. the error persists. this is puzzling.
>
> Cheers, Phil
prev parent reply other threads:[~2020-02-03 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 13:54 invalid read in dyslexicatheist
2020-02-03 16:31 ` Phil Sutter
2020-02-03 17:14 ` dyslexicatheist
2020-02-03 17:30 ` Phil Sutter
2020-02-03 17:49 ` dyslexicatheist [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='s7HX6aItJNJ0k3vJDOdNMEIR5DZxNsav0EwjPqFGroEYHSRmMrGoNy6SX_gHXvSatbsTt1yNihtxUXK_ARVqtWmAsDhmD5fudDnu4mA8Tro=@protonmail.com' \
--to=dyslexicatheist@protonmail.com \
--cc=netfilter-devel@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).