[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170123.104727.1594805087752706376.davem@davemloft.net>
Date: Mon, 23 Jan 2017 10:47:27 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: steffen.klassert@...unet.com
Cc: cernekee@...omium.org, herbert@...dor.apana.org.au,
paul@...l-moore.com, sds@...ho.nsa.gov, eparis@...isplace.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
selinux@...ho.nsa.gov, fw@...len.de, fan.du@...driver.com,
dianders@...omium.org, dtor@...omium.org
Subject: Re: [PATCH 0/4] Make xfrm usable by 32-bit programs
From: Steffen Klassert <steffen.klassert@...unet.com>
Date: Mon, 23 Jan 2017 10:35:17 +0100
> So this creates new incompatibilities what is another argument against
> this approach. If you really need this, try to implement a full compat
> layer. I think this is the only sane solution for this.
A full compat layer is the only reasonable solution to this problem.
Powered by blists - more mailing lists