From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-182.mta0.migadu.com (out-182.mta0.migadu.com [91.218.175.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DF7752264A9; Wed, 28 Jan 2026 19:09:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.182 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769627351; cv=none; b=E1N5aWYuGRwG+0IksfklNcYybS+ldPfHglpsA15hOn8dUhHLmC5hcp4itki6an0OLiLlm3Z1gudaBHnT2zNF8ugsvhkNoI0Y0JZuqpfvGw/daemMWJQbWxldZkrpZr3Ttqh/UmSqrdYvYWrAiNg1se58aro8CqoXNU5XCJ7YeM8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769627351; c=relaxed/simple; bh=4F1TG6+WlGTBF/WCPp6MXY9LYYj2ZXbTcfmFt02NhMk=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=CK7w42pfynqF+Bt1vFR/EJIge+TwoTQNwOxF6KDTlI8SNWH9TnFe8jGFK6s1xM/5z0G3rERjlIJbhj+phMvvLEeYKBrz/smi8Mufu4IRWjjGFfQTncGbAEgzD4XLNPpYiArlKm0urtDs3GIZY9+isD2ZXD0teY2n2TfYQn3gw30= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=QQfkmD5l; arc=none smtp.client-ip=91.218.175.182 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="QQfkmD5l" Message-ID: <7dbcc5d5-476b-46e5-9e4b-b260d24a51a1@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1769627347; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Uoce2O4bq+uQodOB69TrcPt+OZtvkCKYOFmKW88WqjE=; b=QQfkmD5lsHJq3o87CYC128K2gTqM8Je0n3mmDb7+VkG836yXHnF3KY7huFJiwuXOFZwF6+ 84fkXG22+popIKJZno2KmoEGOUfWcQ8vQiZtngJ54CILBc359vKQ7gzGPFZ8B1BKhImMSl PryoO/gGwx1UTolmy4wP1qSn/KnXi4E= Date: Wed, 28 Jan 2026 11:08:54 -0800 Precedence: bulk X-Mailing-List: linux-kselftest@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH bpf-next v2 1/3] bpf: Add bpf_arch_supports_fsession() To: Alexei Starovoitov , Chris Mason Cc: bot+bpf-ci@kernel.org, bpf , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Eduard , Song Liu , Yonghong Song , John Fastabend , KP Singh , Stanislav Fomichev , Hao Luo , Jiri Olsa , Puranjay Mohan , Xu Kuohai , Catalin Marinas , Will Deacon , Shuah Khan , Menglong Dong , linux-arm-kernel , LKML , "open list:KERNEL SELFTEST FRAMEWORK" , kernel-patches-bot@fb.com, Martin KaFai Lau References: <20260128150112.8873-2-leon.hwang@linux.dev> <65231eeb-1f00-4af2-9234-a290ea3f6585@meta.com> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Ihor Solodrai In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT On 1/28/26 10:49 AM, Alexei Starovoitov wrote: > On Wed, Jan 28, 2026 at 9:34 AM Ihor Solodrai wrote: >> >> On 1/28/26 7:35 AM, Chris Mason wrote: >>> >>> >>> On 1/28/26 10:26 AM, bot+bpf-ci@kernel.org wrote: >>>>> diff --git a/arch/x86/net/bpf_jit_comp.c b/arch/x86/net/bpf_jit_comp.c >>>>> index 5a075e06cf..070ba80e39 100644 >>>>> --- a/arch/x86/net/bpf_jit_comp.c >>>>> +++ b/arch/x86/net/bpf_jit_comp.c >>>>> @@ -4112,3 +4112,8 @@ bool bpf_jit_supports_timed_may_goto(void) >>>>> { >>>>> return true; >>>>> } >>>>> + >>>>> +bool bpf_jit_supports_fsession(void) >>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^ >>>> This is the actual function name in the code. >>> >>> Ihor, I think the script parsing review-inline.txt chopped off the >>> part of the review where AI was complaining about the commit message? >> >> This is the email body pre-processing in KPD, yes. >> >> At some point we decided to remove the commit message before sending >> an email, but now that AI reviews the messages too, I think we should >> just send the generated review-inline.txt as is. >> >> Alexei, wdyt? > > I think KPD is only supposed to trim the header until 'diff ..' line. > In this case there is no 'diff', so I'm not sure why it trimmed so much. There is. Here is the PR comment with the review: https://github.com/kernel-patches/bpf/pull/10868#issuecomment-3811930805 KPD trimmed everything before the first "> diff" occurrence, as expected. I'll try to fix this up in KPD. We should probably search for the first line starting with "> " (a quote start) to trim the header correctly. Alternatively, AI can be prompted to avoid generating the header in review-inline.txt, but that's probably less reliable. And maybe it is useful for local runs, idk. > > commit sha... > Author: ... > > are useless in email reply, so we should still trim them.