From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-03.1984.is (mail-03.1984.is [93.95.224.70]) (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 A22F3317163; Mon, 18 May 2026 10:09:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=93.95.224.70 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779098980; cv=none; b=WWrdMb5SSGOADJckMwaQB06TzYiOoYi2hW1Hs+OwO/mx3ZwwBP6GjKKHiNNSldbtUqulCSx1R2i0J6oAbXxDKtcQ9Fx5nFJbOQ1KRgXwHqw3jPX4xfWEaLUnO3wguKlad4svaQzDspyrf9LZJImRNvPV2lJccHdRF7LIWSWyh+Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779098980; c=relaxed/simple; bh=xx5xGxZ0HbjQ/uTeoMm8qFIQ+IOXXdvxDFKs0PexdL4=; h=From:To:Cc:Subject:In-Reply-To:Message-ID:Date; b=urHq+lp3f7WllpdspdyXSHzE5macabqCOMj6lBCXmIqnft2D7//d4yHEkgRzhz9Gz2aYjWozfSRGqSf2SAtqyNJFTb6RZ2X+ZnmGPewRcw1WbCGLofTI8OB06E1X5aCa3MGaPmGJI8LrEsi/JyRRd+naWbkfw3DNh6ShyBawzIE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=berkoc.com; spf=pass smtp.mailfrom=berkoc.com; dkim=pass (2048-bit key) header.d=berkoc.com header.i=@berkoc.com header.b=q/JJrviT; dkim=temperror (0-bit key) header.d=berkoc.com header.i=@berkoc.com header.b=efuWtV7H; arc=none smtp.client-ip=93.95.224.70 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=berkoc.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=berkoc.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=berkoc.com header.i=@berkoc.com header.b="q/JJrviT"; dkim=temperror (0-bit key) header.d=berkoc.com header.i=@berkoc.com header.b="efuWtV7H" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=berkoc.com; s=1984; h=Date:Message-ID:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=qOZcHzFQs6+ZPH5VLzN8MPVqCvbGjRE9wSlF/Xi0stA=; b=q/JJrviTJsLTKAautR0kGBcNqR V3MGki5YSz+tQrjD49JC+nH5Kwxp+14K11uLC0j2DXtjB2HXJk2OPl+EIjMfKxAq8gTg0WKzciCj2 yy9a0oaUwYcOdO/oRxyJbSFTdK9AxVlQg9TgS/6iF1zNhaCoUzJYtthDlyHT+OuC6H77atwnd5VaP NfwwriS+BFTxs3y7BYRMUWxOkuv/QqHfZ/ZbJz2287BFS24lNljlYThHA38cHPGd9CAzdQbcwKiWj QbNlwgOWYlznhvFnNIGUkfQqsaGum7N0NNGYaa4U8C9DskONtTMTioINIw1b9ma2OuX5Vn8pvLvw7 N+o4MxkQ==; Received: from localhost by mail-03.1984.is with utf8esmtp (Exim 4.96) (envelope-from ) id 1wOuuc-002Owt-3A; Mon, 18 May 2026 10:09:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berkoc.com; i=@berkoc.com; q=dns/txt; s=me; t=1779098964; h=message-id : date : subject : cc : to : from : sender : reply-to; bh=qOZcHzFQs6+ZPH5VLzN8MPVqCvbGjRE9wSlF/Xi0stA=; b=efuWtV7HAkQM3i/t2IWKoWSwn8mzRDJI3eLTatE8vkojfZI8sW5W/zwOdkwsLkEneYkb7 OjpblLXvYmar1MbFC95yTvpddv+1cV7pHrDxLFakfkjoRh4RnGIaJSDvpC5fgliMwbLWVW9 SON2+Ll8c8TYw1d9DPNsxwFbyxxOkbBk1mGhC9/3/ZcAubvd49vMVNuU0+xEb0YzLVh3bLp 0mYYnRmexp1Eza1Clyadls1C/Q46aBs+GjkOrBzwTQAfOXTbI3Id/fn8LVnhKVNGNvPzglj zemNh6jTAEVPYXasrR9FbIaiUfjllgX5e2c2vh3d5l+MWSGnIHkM5OugWhRw== From: Berkant Koc To: Vincent Mailhol Cc: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] can: peak_usb: validate URB length in pcan_usb_fd_decode_buf() In-Reply-To: Message-ID: <177909896433.60730.7315497633021818819@berkoc.com> Date: Mon, 18 May 2026 12:09:24 +0200 X-Spam-Score: -0.2 (/) X-Authenticated-User: me@berkoc.com X-Sender-Address: me@berkoc.com Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Vincent, Thanks for the input on both points. Let me work through them and share where I land. > Your message doesn't follow the mailing list etiquette > [...] > kernel mailing lists exclusively require that all communication is > sent as interleaved quoted replies. For context: the previous message was a tool-disclosure reply you'd requested via private CC, not a patch revision. I had treated those two formats differently. Going forward, I'll keep both in interleaved- quoted format on-list, as in this reply. > Is this answer also AI generated? If yes, please don't directly copy > paste AI answers to the mailing list. We expect you to add value to > the AI generated output. To set the record straight: the tool-description paragraph is template text I maintain under version control for tool-disclosure requests across multiple maintainer threads, not LLM output. The methodology section (peak_usb seed commit, pattern scan across drivers/net/can/usb/, manual reproduction with synthetic short URBs) was hand-written from my notes at submission time. Agreed that posting unaltered template text on-list reads the same as LLM-paste from a reader's perspective. I'll rewrite tool-disclosure sections in-thread from now on so the substance is fresh per maintainer. > Ack. Please use that tag. Confirmed. v2 of the peak_usb series will carry: Assisted-by: Claude:claude-opus-4-7 berkoc-pipeline in the trailer. Same convention going forward across all my submissions, in line with the kernel AI-tooling policy. Appreciate the feedback. I revert back to you with the v2 of the peak_usb series and look forward to your review. Best regards, Berkant