Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #69155 > unrolled thread

Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON

Back to article view | Back to linux.debian.kernel

Contents

  Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON Ard Biesheuvel <ardb@kernel.org> - 2021-01-16 10:50 +0100
    Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON Diederik de Haas <didi.debian@cknow.org> - 2021-01-16 18:30 +0100
      Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON Ard Biesheuvel <ardb@kernel.org> - 2021-01-16 18:40 +0100
        Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON Ard Biesheuvel <ardb@kernel.org> - 2021-01-23 11:10 +0100
          Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON Diederik de Haas <didi.debian@cknow.org> - 2021-01-23 15:20 +0100
            Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON Vincent Blut <vincent.debian@free.fr> - 2021-01-23 17:10 +0100
              Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON Diederik de Haas <didi.debian@cknow.org> - 2021-01-23 18:10 +0100
                Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON Vincent Blut <vincent.debian@free.fr> - 2021-01-23 18:40 +0100
    Processed: Re: Bug#980214: linux-image-5.10.0-1-arm64: please  enable CONFIG_CRYPTO_NHPOLY1305_NEON "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-01-23 15:20 +0100
    Bug#980214: Fix found version Diederik de Haas <didi.debian@cknow.org> - 2021-01-23 15:40 +0100
    Processed: Fix found version "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-01-23 15:40 +0100
    Bug#980214: marked as done (linux-image-5.10.0-1-arm64: please  enable CONFIG_CRYPTO_NHPOLY1305_NEON) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-02-06 09:40 +0100

#69155 — Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON

Package: src:linux
Version: 5.10.4-1
Severity: normal

Dear Maintainer,

Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64 builds of
the Linux kernel. This allows platforms that do not support AES instructions
(such as Raspberry Pi 3/4) to enable efficient block device encryption, using
the 'adiantum' template.

Kind regards,
Ard.


-- Package-specific info:
** Version:
Linux version 5.10.0-1-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-3) 10.2.1 20201224, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.10.4-1 (2020-12-31)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-arm64 root=UUID=62fa7565-f531-4b0f-9311-59cb70ba2c93 ro quiet

** Not tainted

** Kernel log:
[    3.822227] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    3.822239] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.822247] usb usb1: Product: xHCI Host Controller
[    3.822254] usb usb1: Manufacturer: Linux 5.10.0-1-arm64 xhci-hcd
[    3.822261] usb usb1: SerialNumber: PNP0D10:00
[    3.822910] hub 1-0:1.0: USB hub found
[    3.822979] hub 1-0:1.0: 1 port detected
[    3.823542] xhci-hcd PNP0D10:00: xHCI Host Controller
[    3.823572] xhci-hcd PNP0D10:00: new USB bus registered, assigned bus number 2
[    3.823591] xhci-hcd PNP0D10:00: Host supports USB 3.0 SuperSpeed
[    3.823752] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.823936] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    3.823945] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.823953] usb usb2: Product: xHCI Host Controller
[    3.823960] usb usb2: Manufacturer: Linux 5.10.0-1-arm64 xhci-hcd
[    3.823966] usb usb2: SerialNumber: PNP0D10:00
[    3.824623] hub 2-0:1.0: USB hub found
[    3.824677] hub 2-0:1.0: 4 ports detected
[    3.838859] bcmgenet BCM6E4E:00 enabcm6e4ei0: renamed from eth0
[    4.157943] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    4.312580] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[    4.312595] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    4.312603] usb 1-1: Product: USB2.0 Hub
[    4.314265] hub 1-1:1.0: USB hub found
[    4.314540] hub 1-1:1.0: 4 ports detected
[    4.438232] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[    4.460809] usb 2-2: New USB device found, idVendor=18a5, idProduct=0237, bcdDevice= 5.10
[    4.460819] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.460827] usb 2-2: Product: Portable USB 3.0 Drive
[    4.460835] usb 2-2: Manufacturer: Verbatim
[    4.460842] usb 2-2: SerialNumber: 1407010003245394
[    4.498931] SCSI subsystem initialized
[    4.513467] usb-storage 2-2:1.0: USB Mass Storage device detected
[    4.514813] scsi host0: usb-storage 2-2:1.0
[    4.515356] usbcore: registered new interface driver usb-storage
[    4.520563] usbcore: registered new interface driver uas
[    4.673929] libphy: bcmgenet MII bus: probed
[    4.673945] unimac-mdio unimac-mdio: Broadcom UniMAC MDIO bus
[    5.535323] scsi 0:0:0:0: Direct-Access     Samsung  SSD 850 PRO      EXM0 PQ: 0 ANSI: 6
[    5.556933] sd 0:0:0:0: [sda] 500118188 512-byte logical blocks: (256 GB/238 GiB)
[    5.557351] sd 0:0:0:0: [sda] Write Protect is off
[    5.557362] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[    5.557768] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.576531]  sda: sda1 sda2
[    5.578991] sd 0:0:0:0: [sda] Attached SCSI disk
[    5.612373] random: fast init done
[    6.084383] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    6.358453] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[    6.530927] systemd[1]: Inserted module 'autofs4'
[    6.593403] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    6.594215] systemd[1]: Detected architecture arm64.
[    6.622998] systemd[1]: Set hostname to <rpi4>.
[    7.062138] random: systemd: uninitialized urandom read (16 bytes read)
[    7.067659] random: systemd: uninitialized urandom read (16 bytes read)
[    7.071927] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    7.072502] random: systemd: uninitialized urandom read (16 bytes read)
[    7.072985] systemd[1]: Listening on Journal Audit Socket.
[    7.073615] systemd[1]: Listening on Journal Socket (/dev/log).
[    7.075141] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    7.076570] systemd[1]: Created slice User and Session Slice.
[    7.076698] systemd[1]: Reached target Slices.
[    7.077261] systemd[1]: Listening on udev Kernel Socket.
[    7.230826] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
[    7.446370] systemd-journald[220]: Received request to flush runtime journal from PID 1
[    7.956977] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    8.064863] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[    8.140177] cryptd: max_cpu_qlen set to 1000
[    8.572745] random: crng init done
[    8.572758] random: 7 urandom warning(s) missed due to ratelimiting
[    8.626854] Bluetooth: Core ver 2.22
[    8.627007] NET: Registered protocol family 31
[    8.627015] Bluetooth: HCI device and connection manager initialized
[    8.628647] Bluetooth: HCI socket layer initialized
[    8.628663] Bluetooth: L2CAP socket layer initialized
[    8.628699] Bluetooth: SCO socket layer initialized
[    8.702144] Bluetooth: HCI UART driver ver 2.3
[    8.702159] Bluetooth: HCI UART protocol H4 registered
[    8.702296] Bluetooth: HCI UART protocol LL registered
[    8.702304] Bluetooth: HCI UART protocol ATH3K registered
[    8.702367] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    8.702570] Bluetooth: HCI UART protocol Intel registered
[    8.702882] Bluetooth: HCI UART protocol Broadcom registered
[    8.702953] Bluetooth: HCI UART protocol QCA registered
[    8.702960] Bluetooth: HCI UART protocol AG6XX registered
[    8.703006] Bluetooth: HCI UART protocol Marvell registered
[    8.764517] audit: type=1400 audit(1604510514.143:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=426 comm="apparmor_parser"
[    8.764549] audit: type=1400 audit(1604510514.143:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=426 comm="apparmor_parser"
[    8.765026] audit: type=1400 audit(1604510514.151:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=427 comm="apparmor_parser"
[    8.765048] audit: type=1400 audit(1604510514.151:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=427 comm="apparmor_parser"
[    8.765065] audit: type=1400 audit(1604510514.151:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=427 comm="apparmor_parser"
[    8.783189] audit: type=1400 audit(1604510514.171:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/aarch64-linux-gnu/lightdm/lightdm-guest-session" pid=425 comm="apparmor_parser"
[    8.783216] audit: type=1400 audit(1604510514.171:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/aarch64-linux-gnu/lightdm/lightdm-guest-session//chromium" pid=425 comm="apparmor_parser"
[    9.501478] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    9.501491] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[    9.914262] bcmgenet BCM6E4E:00: configuring instance for external RGMII (RX delay)
[    9.914619] bcmgenet BCM6E4E:00 enabcm6e4ei0: Link is Up - 1Gbps/Full - flow control rx/tx
[    9.914849] IPv6: ADDRCONF(NETDEV_CHANGE): enabcm6e4ei0: link becomes ready
[   10.175742] NET: Registered protocol family 5
[142340.069707] tun: Universal TUN/TAP device driver, 1.6
[1173543.653652] NET: Registered protocol family 38

** Model information

** Loaded modules:
nhpoly1305
adiantum
libpoly1305
ecb
xts
twofish_generic
twofish_common
serpent_generic
cbc
algif_skcipher
af_alg
tun
appletalk
psnap
llc
wireguard
libchacha20poly1305
chacha_neon
poly1305_neon
ip6_udp_tunnel
udp_tunnel
libblake2s
libcurve25519_generic
libchacha
libblake2s_generic
nft_counter
nft_chain_nat
xt_MASQUERADE
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nft_compat
nf_tables
libcrc32c
hci_uart
nfnetlink
btqca
btrtl
btbcm
btintel
bluetooth
nls_ascii
nls_cp437
vfat
fat
jitterentropy_rng
aes_neon_bs
aes_neon_blk
crypto_simd
cryptd
drbg
aes_arm64
aes_generic
ansi_cprng
sg
ecdh_generic
rfkill
ecc
libaes
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
uas
usb_storage
scsi_mod
broadcom
bcm_phy_lib
mdio_bcm_unimac
xhci_plat_hcd
xhci_hcd
genet
of_mdio
crct10dif_ce
fixed_phy
usbcore
crct10dif_common
libphy
usb_common

** PCI devices:

** USB devices:
Bus 002 Device 002: ID 18a5:0237 Verbatim, Ltd Portable Harddrive
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.0-1-arm64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-5.10.0-1-arm64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
ii  kmod                                    26-1
ii  linux-base                              4.6

Versions of packages linux-image-5.10.0-1-arm64 recommends:
ii  apparmor             2.13.2-10
ii  firmware-linux-free  3.4

Versions of packages linux-image-5.10.0-1-arm64 suggests:
pn  debian-kernel-handbook  <none>
pn  linux-doc-5.10          <none>

Versions of packages linux-image-5.10.0-1-arm64 is related to:
pn  firmware-amd-graphics     <none>
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
pn  firmware-brcm80211        <none>
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
pn  firmware-linux-nonfree    <none>
pn  firmware-misc-nonfree     <none>
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

[toc] | [next] | [standalone]

#69159

[Multipart message — attachments visible in raw view] — view raw

On zaterdag 16 januari 2021 10:42:19 CET Ard Biesheuvel wrote:
> Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64 builds

Is there a reason why it shouldn't be included in armhf builds? If not, then 
I'd like to see it enabled there too.
(And possibly in linux-image-rpi on armel as well?)

[toc] | [prev] | [next] | [standalone]

#69160

On Sat, 16 Jan 2021 at 18:24, Diederik de Haas <didi.debian@cknow.org> wrote:
>
> On zaterdag 16 januari 2021 10:42:19 CET Ard Biesheuvel wrote:
> > Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64 builds
>
> Is there a reason why it shouldn't be included in armhf builds? If not, then
> I'd like to see it enabled there too.
> (And possibly in linux-image-rpi on armel as well?)

Agreed for armhf, assuming CONFIG_CRYPTO_ADIANTUM is already enabled
on those platforms too. For armel, it depends on whether kernel mode
NEON is already enabled in the first place.

[toc] | [prev] | [next] | [standalone]

#69288

On Sat, 16 Jan 2021 at 18:27, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> On Sat, 16 Jan 2021 at 18:24, Diederik de Haas <didi.debian@cknow.org> wrote:
> >
> > On zaterdag 16 januari 2021 10:42:19 CET Ard Biesheuvel wrote:
> > > Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64 builds
> >
> > Is there a reason why it shouldn't be included in armhf builds? If not, then
> > I'd like to see it enabled there too.
> > (And possibly in linux-image-rpi on armel as well?)
>
> Agreed for armhf, assuming CONFIG_CRYPTO_ADIANTUM is already enabled
> on those platforms too. For armel, it depends on whether kernel mode
> NEON is already enabled in the first place.

This is enabled now for armhf but not for arm64:

linux-signed-arm64 (5.10.9+1) unstable; urgency=medium
...
* [arm] Enable CRYPTO_NHPOLY1305_NEON. (closes: #980214)

[toc] | [prev] | [next] | [standalone]

#69296

[Multipart message — attachments visible in raw view] — view raw

Control: reopen -1
Control: found -1 5.10.9+1

On zaterdag 23 januari 2021 11:05:23 CET Ard Biesheuvel wrote:
> On Sat, 16 Jan 2021 at 18:27, Ard Biesheuvel <ardb@kernel.org> wrote:
> > On Sat, 16 Jan 2021 at 18:24, Diederik de Haas <didi.debian@cknow.org> 
wrote:
> > > On zaterdag 16 januari 2021 10:42:19 CET Ard Biesheuvel wrote:
> > > > Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64
> > > > builds
> > > 
> > > Is there a reason why it shouldn't be included in armhf builds? If not,
> > > then I'd like to see it enabled there too.
> > > (And possibly in linux-image-rpi on armel as well?)
> > 
> > Agreed for armhf, assuming CONFIG_CRYPTO_ADIANTUM is already enabled
> > on those platforms too. For armel, it depends on whether kernel mode
> > NEON is already enabled in the first place.
> 
> This is enabled now for armhf but not for arm64:
> 
> linux-signed-arm64 (5.10.9+1) unstable; urgency=medium
> ...
> * [arm] Enable CRYPTO_NHPOLY1305_NEON. (closes: #980214)

I first thought that '[arm]' was a shorthand for various ARM architectures, but 
I just confirmed that it is indeed not fixed/enabled in arm64:
# grep CRYPTO_NHPOLY1305_NEON /boot/config-5.10.0-2-arm64 
# CONFIG_CRYPTO_NHPOLY1305_NEON is not set

[toc] | [prev] | [next] | [standalone]

#69299

[Multipart message — attachments visible in raw view] — view raw

Hi,

Le 2021-01-23 15:00, Diederik de Haas a écrit :
> Control: reopen -1
> Control: found -1 5.10.9+1
> 
> On zaterdag 23 januari 2021 11:05:23 CET Ard Biesheuvel wrote:
> > On Sat, 16 Jan 2021 at 18:27, Ard Biesheuvel <ardb@kernel.org> wrote:
> > > On Sat, 16 Jan 2021 at 18:24, Diederik de Haas <didi.debian@cknow.org> 
> wrote:
> > > > On zaterdag 16 januari 2021 10:42:19 CET Ard Biesheuvel wrote:
> > > > > Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64
> > > > > builds
> > > > 
> > > > Is there a reason why it shouldn't be included in armhf builds? If not,
> > > > then I'd like to see it enabled there too.
> > > > (And possibly in linux-image-rpi on armel as well?)
> > > 
> > > Agreed for armhf, assuming CONFIG_CRYPTO_ADIANTUM is already enabled
> > > on those platforms too. For armel, it depends on whether kernel mode
> > > NEON is already enabled in the first place.
> > 
> > This is enabled now for armhf but not for arm64:
> > 
> > linux-signed-arm64 (5.10.9+1) unstable; urgency=medium
> > ...
> > * [arm] Enable CRYPTO_NHPOLY1305_NEON. (closes: #980214)
> 
> I first thought that '[arm]' was a shorthand for various ARM architectures, but 
> I just confirmed that it is indeed not fixed/enabled in arm64:
> # grep CRYPTO_NHPOLY1305_NEON /boot/config-5.10.0-2-arm64 
> # CONFIG_CRYPTO_NHPOLY1305_NEON is not set

Indeed. I just sent a MR¹ to fix this.

Cheers,
Vincent

¹ https://salsa.debian.org/kernel-team/linux/-/merge_requests/312

[toc] | [prev] | [next] | [standalone]

#69300

[Multipart message — attachments visible in raw view] — view raw

On zaterdag 23 januari 2021 17:00:25 CET Vincent Blut wrote:
> Hi,
> 
> Le 2021-01-23 15:00, Diederik de Haas a écrit :
> > Control: reopen -1
> > Control: found -1 5.10.9+1
> > 
> > On zaterdag 23 januari 2021 11:05:23 CET Ard Biesheuvel wrote:
> > > On Sat, 16 Jan 2021 at 18:27, Ard Biesheuvel <ardb@kernel.org> wrote:
> > > > On Sat, 16 Jan 2021 at 18:24, Diederik de Haas <didi.debian@cknow.org>
> > 
> > wrote:
> > > > > On zaterdag 16 januari 2021 10:42:19 CET Ard Biesheuvel wrote:
> > > > > > Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64
> > > > > > builds
> > > > > 
> > > > > Is there a reason why it shouldn't be included in armhf builds? If
> > > > > not,
> > > > > then I'd like to see it enabled there too.
> > > > > (And possibly in linux-image-rpi on armel as well?)
> > > > 
> > > > Agreed for armhf, assuming CONFIG_CRYPTO_ADIANTUM is already enabled
> > > > on those platforms too. For armel, it depends on whether kernel mode
> > > > NEON is already enabled in the first place.
> > > 
> > > This is enabled now for armhf but not for arm64:
> > > 
> > > linux-signed-arm64 (5.10.9+1) unstable; urgency=medium
> > > ...
> > > * [arm] Enable CRYPTO_NHPOLY1305_NEON. (closes: #980214)
> > 
> > I first thought that '[arm]' was a shorthand for various ARM
> > architectures, but I just confirmed that it is indeed not fixed/enabled
> > in arm64:
> > # grep CRYPTO_NHPOLY1305_NEON /boot/config-5.10.0-2-arm64
> > # CONFIG_CRYPTO_NHPOLY1305_NEON is not set
> 
> Indeed. I just sent a MR¹ to fix this.
> 
> Cheers,
> Vincent
> 
> ¹ https://salsa.debian.org/kernel-team/linux/-/merge_requests/312

$ grep CRYPTO_NHPOLY1305_NEON /boot/config-5.10.0-2-armmp

didn't give a result, so it looks like it's also not enabled on armhf?

[toc] | [prev] | [next] | [standalone]

#69301

[Multipart message — attachments visible in raw view] — view raw

Le 2021-01-23 18:04, Diederik de Haas a écrit :
> On zaterdag 23 januari 2021 17:00:25 CET Vincent Blut wrote:
> > Hi,
> > 
> > Le 2021-01-23 15:00, Diederik de Haas a écrit :
> > > Control: reopen -1
> > > Control: found -1 5.10.9+1
> > > 
> > > On zaterdag 23 januari 2021 11:05:23 CET Ard Biesheuvel wrote:
> > > > On Sat, 16 Jan 2021 at 18:27, Ard Biesheuvel <ardb@kernel.org> wrote:
> > > > > On Sat, 16 Jan 2021 at 18:24, Diederik de Haas <didi.debian@cknow.org>
> > > 
> > > wrote:
> > > > > > On zaterdag 16 januari 2021 10:42:19 CET Ard Biesheuvel wrote:
> > > > > > > Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64
> > > > > > > builds
> > > > > > 
> > > > > > Is there a reason why it shouldn't be included in armhf builds? If
> > > > > > not,
> > > > > > then I'd like to see it enabled there too.
> > > > > > (And possibly in linux-image-rpi on armel as well?)
> > > > > 
> > > > > Agreed for armhf, assuming CONFIG_CRYPTO_ADIANTUM is already enabled
> > > > > on those platforms too. For armel, it depends on whether kernel mode
> > > > > NEON is already enabled in the first place.
> > > > 
> > > > This is enabled now for armhf but not for arm64:
> > > > 
> > > > linux-signed-arm64 (5.10.9+1) unstable; urgency=medium
> > > > ...
> > > > * [arm] Enable CRYPTO_NHPOLY1305_NEON. (closes: #980214)
> > > 
> > > I first thought that '[arm]' was a shorthand for various ARM
> > > architectures, but I just confirmed that it is indeed not fixed/enabled
> > > in arm64:
> > > # grep CRYPTO_NHPOLY1305_NEON /boot/config-5.10.0-2-arm64
> > > # CONFIG_CRYPTO_NHPOLY1305_NEON is not set
> > 
> > Indeed. I just sent a MR¹ to fix this.
> > 
> > Cheers,
> > Vincent
> > 
> > ¹ https://salsa.debian.org/kernel-team/linux/-/merge_requests/312
> 
> $ grep CRYPTO_NHPOLY1305_NEON /boot/config-5.10.0-2-armmp
> 
> didn't give a result, so it looks like it's also not enabled on armhf?

Oh I see, support for NEON in kernel mode is disabled.

[toc] | [prev] | [next] | [standalone]

#69295 — Processed: Re: Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON

Processing control commands:

> reopen -1
Bug #980214 {Done: Salvatore Bonaccorso <carnil@debian.org>} [src:linux] linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions linux/5.10.9-1.
> found -1 5.10.9+1
Bug #980214 [src:linux] linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON
The source 'linux' and version '5.10.9+1' do not appear to match any binary packages
Marked as found in versions linux/5.10.9+1.

-- 
980214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980214
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#69297 — Bug#980214: Fix found version

[Multipart message — attachments visible in raw view] — view raw

Control: notfound -1 5.10.9+1
Control: found -1 5.10.9-1

[toc] | [prev] | [next] | [standalone]

#69298 — Processed: Fix found version

Processing control commands:

> notfound -1 5.10.9+1
Bug #980214 [src:linux] linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON
The source 'linux' and version '5.10.9+1' do not appear to match any binary packages
No longer marked as found in versions linux/5.10.9+1.
> found -1 5.10.9-1
Bug #980214 [src:linux] linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON
Marked as found in versions linux/5.10.9-1.

-- 
980214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980214
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#69444 — Bug#980214: marked as done (linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sat, 06 Feb 2021 08:33:48 +0000
with message-id <E1l8J2K-0006mk-2D@fasolo.debian.org>
and subject line Bug#980214: fixed in linux 5.10.13-1
has caused the Debian Bug report #980214,
regarding linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
980214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980214
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web