BPF List
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH iproute2-next v2] lib/bpf_legacy: Use userspace SHA-1 code instead of AF_ALG
Date: Thu, 18 Dec 2025 12:58:35 -0700	[thread overview]
Message-ID: <316f974b-50e8-4d24-b422-7b981fb84ecf@kernel.org> (raw)
In-Reply-To: <20251217234447.GA89113@google.com>

On 12/17/25 4:44 PM, Eric Biggers wrote:
>> If we are going to entertain removing AF_ALG code, we should apply the
>> patch to iproute2-next at the beginning of a dev cycle to give maximum
>> time for testing before it rolls out.
> 
> Any insight into when that would be?
> 


re-send it now.


  reply	other threads:[~2025-12-18 19:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 19:46 [PATCH iproute2-next v2] lib/bpf_legacy: Use userspace SHA-1 code instead of AF_ALG Eric Biggers
2025-10-01 22:59 ` Alexei Starovoitov
2025-10-01 23:33   ` Eric Biggers
2025-10-02 17:12     ` Alexei Starovoitov
2025-10-02 17:36       ` Eric Biggers
2025-10-02 17:53         ` Alexei Starovoitov
2025-11-12  4:07 ` Eric Biggers
2025-11-16 17:45   ` David Ahern
2025-12-17 23:44     ` Eric Biggers
2025-12-18 19:58       ` David Ahern [this message]
2025-11-12 20:12 ` Stephen Hemminger
2025-11-12 20:22   ` Eric Biggers
2025-11-13  7:25   ` Ard Biesheuvel
2025-11-13  8:51     ` Simon Richter
2025-11-13 15:35       ` Ard Biesheuvel

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=316f974b-50e8-4d24-b422-7b981fb84ecf@kernel.org \
    --to=dsahern@kernel.org \
    --cc=ardb@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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