From: John Wood <john.wood@gmx.com>
To: Kees Cook <keescook@chromium.org>
Cc: John Wood <john.wood@gmx.com>, kernel-hardening@lists.openwall.com
Subject: Re: [RFC PATCH 0/9] Fork brute force attack mitigation (fbfam)
Date: Sun, 6 Sep 2020 18:11:54 +0200 [thread overview]
Message-ID: <20200906142542.GV4823@ubuntu> (raw)
In-Reply-To: <20200906142029.6348-1-john.wood@gmx.com>
Sorry, but the problems with me email account are not resolved.
Please, don't reply to this message.
Apologies.
I try to send the full patch serie as soon as possible.
For now Matthew Wilcox <willy@infradead.org> will sent the serie.
Thanks.
John Wood
next prev parent reply other threads:[~2020-09-06 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 14:20 [RFC PATCH 0/9] Fork brute force attack mitigation (fbfam) John Wood
2020-09-06 16:11 ` John Wood [this message]
2020-09-06 20:25 ` Kees Cook
2020-09-07 18:07 ` John Wood
-- strict thread matches above, loose matches on Subject: below --
2020-09-06 12:15 John Wood
2020-09-06 13:52 ` John Wood
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=20200906142542.GV4823@ubuntu \
--to=john.wood@gmx.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.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 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).