From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, abbotti@mev.co.uk
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4.y] comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large
Date: Fri, 25 Jul 2025 19:26:06 -0400 [thread overview]
Message-ID: <1753465192-da4c3231@stable.kernel.org> (raw)
In-Reply-To: <20250724182218.292203-1-abbotti@mev.co.uk>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
❌ Build failures detected
The upstream commit SHA1 provided is correct: 08ae4b20f5e82101d77326ecab9089e110f224cc
Status in newer kernel trees:
6.15.y | Not found
6.12.y | Not found
6.6.y | Not found
6.1.y | Not found
5.15.y | Not found
5.10.y | Not found
Note: The patch differs from the upstream commit:
---
1: 08ae4b20f5e8 < -: ------------ comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large
-: ------------ > 1: 480e150b6535 comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-5.4.y | Success | Failed |
Build Errors:
origin/linux-5.4.y:
Build error: Building current HEAD with log output
Build x86: exited with code 2
Cleaning up worktrees...
Cleaning up worktrees...
Cleaning up worktrees...
Cleaning up worktrees...
next prev parent reply other threads:[~2025-07-25 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 18:22 [PATCH 5.4.y] comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large Ian Abbott
2025-07-25 23:26 ` Sasha Levin [this message]
2025-07-28 12:13 ` Ian Abbott
2025-07-28 12:18 ` [PATCH v2 5.4] " Ian Abbott
2025-07-28 14:57 ` Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1753465192-da4c3231@stable.kernel.org \
--to=sashal@kernel.org \
--cc=abbotti@mev.co.uk \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.