From: Dan Carpenter <dan.carpenter at oracle.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH][next] mptcp: fix a dereference of pointer before msk is null checked.
Date: Mon, 09 Nov 2020 17:57:58 +0300 [thread overview]
Message-ID: <20201109145758.GP18329@kadam> (raw)
In-Reply-To: b5c267c1-f116-419c-92c9-88a56f9a3b51@canonical.com
[-- Attachment #1: Type: text/plain, Size: 532 bytes --]
On Mon, Nov 09, 2020 at 02:38:47PM +0000, Colin Ian King wrote:
> On 09/11/2020 14:36, Geliang Tang wrote:
> > Hi Colin,
> >
> > Thanks for your patch. But this bug is reported by Dan Carpenter to MPTCP
> > ML earlier, and I have already sent out a fix in MPTCP ML for review. So
> > your fix is duplicated. I'm sorry.
>
> Oh I missed Dan's fix. No problem, glad it is fixed. :-)
No, I didn't send a fix, just the bug report. I normally don't send
bug reports to the kernel-janitors list.
regards,
dan carpenter
next reply other threads:[~2020-11-09 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 14:57 Dan Carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-11 19:23 [MPTCP] Re: [PATCH][next] mptcp: fix a dereference of pointer before msk is null checked Colin Ian King
2020-11-11 18:49 Mat Martineau
2020-11-09 14:38 Colin Ian King
2020-11-09 14:36 Geliang Tang
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=20201109145758.GP18329@kadam \
--to=unknown@example.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.