From nobody Tue Apr 2 13:28:50 2024 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V87yf5vvhz5GcJF for ; Tue, 2 Apr 2024 13:29:30 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V87yd6LSpz42mZ for ; Tue, 2 Apr 2024 13:29:29 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of ccfreebsd@gmail.com designates 209.85.208.180 as permitted sender) smtp.mailfrom=ccfreebsd@gmail.com Received: by mail-lj1-f180.google.com with SMTP id 38308e7fff4ca-2d48f03a8bbso53203301fa.0 for ; Tue, 02 Apr 2024 06:29:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712064568; x=1712669368; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=nkto7E8EnRiV3pifL/G+PeEeMfZnc2t1wKfmSam7ipY=; b=gG4X7R7a3AXKZWyUH5LNe8VEO/Zpb1PAQ/y91VZp1ckaHv0LdhdHi6pB1BFttVq+RC LzBt47J1PxWHKp6Td+PoyJKNRlklYnFFu0uiXQXysjmO+MjdJ9NginvJMFAA8SPluowp aPTMD26GpA5udwRJFx+FHtSAV4fqL40iD3leOxZjkQeZ6XHQAWh4BHBbP/ifbVuuDeZa ECrxGXTulXYxUHy84ugMQwF/MGcCz0QvdKRihSRCu2ZDcQj3eY45q9LbErUs2Qc0xGj0 g5nveaLICHhRgccyvytIDIfD5/UDFhv6ipC7+hvG5Ktx2yl4UGIrlLZ3GsTjQ5SfmrTJ FlMQ== X-Gm-Message-State: AOJu0Ywr/KKXhjDWWyZie/Q5RFcPIXXq4rKkDGv+ROzkzb7rIi32Qn1x R+y0/G6wFAMamFAExLfJGvMqPkBKrGLh2zJKIZuLzhRIA9q3z8TLd6qHJJBoS38= X-Google-Smtp-Source: AGHT+IGnHob0/2tquCn3H9lED6VhK57ZcJOt1KKTfhmXqQ7ddEyT2hcPYVOi6Upbf9up53B2RXI+dg== X-Received: by 2002:a2e:a1c7:0:b0:2d7:1cd2:d382 with SMTP id c7-20020a2ea1c7000000b002d71cd2d382mr3851272ljm.15.1712064567451; Tue, 02 Apr 2024 06:29:27 -0700 (PDT) Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com. [209.85.167.52]) by smtp.gmail.com with ESMTPSA id w2-20020a2e8202000000b002d6a231a0c3sm1664352ljg.10.2024.04.02.06.29.27 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Apr 2024 06:29:27 -0700 (PDT) Received: by mail-lf1-f52.google.com with SMTP id 2adb3069b0e04-515b43b39fdso4441159e87.1 for ; Tue, 02 Apr 2024 06:29:27 -0700 (PDT) X-Received: by 2002:a05:6512:788:b0:515:cff1:9e30 with SMTP id x8-20020a056512078800b00515cff19e30mr4111874lfr.18.1712064567096; Tue, 02 Apr 2024 06:29:27 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 From: Cheng Cui Date: Tue, 2 Apr 2024 09:28:50 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Weekly Development report(Mar 25 ~ Mar 29) on the iwlwifi WiFi project To: wireless@freebsd.org Content-Type: multipart/alternative; boundary="0000000000005ade7006151d185b" X-Spamd-Bar: - X-Spamd-Result: default: False [-1.38 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.52)[0.522]; FORGED_SENDER(0.30)[cc@freebsd.org,ccfreebsd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[wireless@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[cc@freebsd.org,ccfreebsd@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.180:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.180:from,209.85.167.52:received] X-Rspamd-Queue-Id: 4V87yd6LSpz42mZ --0000000000005ade7006151d185b Content-Type: text/plain; charset="UTF-8" As mentioned earlier there is a problem with the HW encryption per packet once `LKPI_80211_HW_CRYPTO` is defined. This problem (tracking in PR 277996 ) is on top of the patch D44463 , which I would welcome more feedback. Current investigation confirms that HW key setup in firmware/driver is successful, 80211 key mapping between the FreeBSD and the LinuxKPI is correct, and the HW key encryption stub in skbuf for the driver is available until the driver handles it. After sync-up with Bjoern, I found this problem only happens in the tx path, not the rx path, which means this is only impacting the tx encryption. My next step is to investigate the tx path with HW encryption in the Linux kernel, and figure out how to check these parameters/flags. Most likely I am going to dump a Linux kernel core file on the point where I am interested to see the internal stats. -- Best Regards, Cheng Cui --0000000000005ade7006151d185b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As mentioned earlier there is a problem with the HW encryp= tion per packet once `LKPI_80211_HW_CRYPTO`=C2=A0is defined. This pro= blem (tracking in PR 277996) is on top of the=C2=A0patch=C2=A0D44463, whic= h I would welcome more feedback. Current investigation confirms that HW key= setup in firmware/driver is successful, 80211 key mapping between the Free= BSD and the LinuxKPI is correct, and the HW key encryption stub in skbuf=C2= =A0for the driver=C2=A0is available until the driver handles it. After sync= -up with Bjoern, I found this problem only happens in the tx path, not the = rx path, which means this is only impacting the tx encryption. My next step= is to investigate the tx path with HW encryption in the Linux kernel, and = figure out how to check these parameters/flags. Most likely I am going to d= ump a Linux kernel core file on the point where I am interested=C2=A0to see= the internal stats.

--
Best Regards,
Che= ng Cui
--0000000000005ade7006151d185b--