Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <1c71e611-42d0-daf6-3ef2-c404561b42f7@redhat.com>
Date:   Mon, 27 Mar 2023 12:54:17 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.7.1
Subject: Re: iwlwifi "memcpy: detected field-spanning write" kernel oops
Content-Language: en-US
To:     Johannes Berg <johannes@sipsolutions.net>,
        Gregory Greenman <gregory.greenman@intel.com>,
        Benjamin Berg <benjamin.berg@intel.com>
Cc:     Kalle Valo <kvalo@kernel.org>,
        linux-wireless <linux-wireless@vger.kernel.org>,
        Kees Cook <keescook@chromium.org>
References: <68760035-7f75-1b23-e355-bfb758a87d83@redhat.com>
 <569b7058d6a9807a98777bf7a0cfc4b3846477d8.camel@sipsolutions.net>
From:   Hans de Goede <hdegoede@redhat.com>
In-Reply-To: <569b7058d6a9807a98777bf7a0cfc4b3846477d8.camel@sipsolutions.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Johannes,

On 3/27/23 11:50, Johannes Berg wrote:
> On Mon, 2023-03-27 at 11:12 +0200, Hans de Goede wrote:
>> Hi All,
>>
>> I have noticed the following iwlwifi oops with kernel 6.2.0 and newer (1):
> 
> Yes, this was noted before and Kees was working on a fix:
> 
> https://lore.kernel.org/linux-wireless/20230218191056.never.374-kees@kernel.org/
> 
> but the discussion was still ongoing and I don't think he posted a final
> version yet.

Thanks for the reply.

Reading the thread I see that this seems to be an actual bug and there are 
some ideas how to fix this, but it needs someone to actually test the fixes.

I hit the reported oops whenever one of my laptops at home connects
to my home router access-point.

So I can reproduce this at will; and given that I hit the oops I assume
that my home network also actually uses the keys setup by the given path,
so I should also be able to test that a fix does not break the wifi
connection by misconfiguring the keys.

So I'm hereby volunteering to test a fix on my setup.

Regards,

Hans