From: Stephan Mueller <smueller@chronox.de>
To: noloader@gmail.com
Cc: linux-crypto@vger.kernel.org
Subject: Re: [ANNOUNCE] libkcapi v0.12.0 released
Date: Fri, 28 Oct 2016 01:04:30 +0200 [thread overview]
Message-ID: <2286347.nnOjI5TozX@tauon.atsec.com> (raw)
In-Reply-To: <CAH8yC8kvADeRgjxkBbdA5aMBDnVVKauTyfS-anaHr+bsF-U1iQ@mail.gmail.com>
Am Donnerstag, 27. Oktober 2016, 18:53:45 CEST schrieb Jeffrey Walton:
Hi Jeffrey,
> >> preprocessor macros we can use to guard it?
> >
> > I am not entirely sure I understand the question.
>
> See, for example,
> https://github.com/openssl/openssl/blob/master/engines/afalg/e_afalg.c
>
> The versions are kind of arbitrary because there's no easy way to tell
> when the gear is available. If I recall from researching things, there
> were two components needed for afalg, and they were supposedly
> available back to later 2.x kernels.
>
> Things should "just work" for 3.x and 4.x kernels. But if "too early"
> a kernel is encountered, then users experience the spectrum from
> compile problems to unexplained runtime errors.
I see. There are guards around zerocopy.
AF_ALG appeared with 2.6.38 / 3.0 which already had zerocopy.
I will try a 3.0 kernel with my current lib to see whether it works out of the
box and apply fixes and guards if it does not.
But I am not sure whether I should guard anything for 2.x kernels where we
know that some folks simply backported the AF_ALG interface.
Thanks a lot for the reminder.
Ciao
Stephan
prev parent reply other threads:[~2016-10-27 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 1:54 [ANNOUNCE] libkcapi v0.12.0 released Stephan Mueller
2016-10-27 2:05 ` Jeffrey Walton
2016-10-27 2:52 ` Stephan Mueller
2016-10-27 22:53 ` Jeffrey Walton
2016-10-27 23:04 ` Stephan Mueller [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=2286347.nnOjI5TozX@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=linux-crypto@vger.kernel.org \
--cc=noloader@gmail.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).