linux-kernel - Re: [PATCH 3/3] dt-bindings: eeprom: at24: Add at24,mac02e4 and at24,mac02e6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240620-bulge-sturdy-cd0f92f05de2@wendy>
Date: Thu, 20 Jun 2024 12:10:32 +0100
From: Conor Dooley <conor.dooley@...rochip.com>
To: <Andrei.Simion@...rochip.com>
CC: <conor@...nel.org>, <brgl@...ev.pl>, <robh@...nel.org>,
	<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <Nicolas.Ferre@...rochip.com>,
	<alexandre.belloni@...tlin.com>, <claudiu.beznea@...on.dev>, <arnd@...db.de>,
	<gregkh@...uxfoundation.org>, <linux-i2c@...r.kernel.org>,
	<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 3/3] dt-bindings: eeprom: at24: Add at24,mac02e4 and
 at24,mac02e6

On Thu, Jun 20, 2024 at 10:45:58AM +0000, Andrei.Simion@...rochip.com wrote:
> On 19.06.2024 20:53, Conor Dooley wrote:
> >> Update regex check and add pattern to match both EEPROMs.
> >>
> >> Signed-off-by: Andrei Simion <andrei.simion@...rochip.com>
> >> ---
> >>  Documentation/devicetree/bindings/eeprom/at24.yaml | 10 +++++++---
> >>  1 file changed, 7 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/Documentation/devicetree/bindings/eeprom/at24.yaml b/Documentation/devicetree/bindings/eeprom/at24.yaml
> >> index 3c36cd0510de..46daa662f6e7 100644
> >> --- a/Documentation/devicetree/bindings/eeprom/at24.yaml
> >> +++ b/Documentation/devicetree/bindings/eeprom/at24.yaml
> >> @@ -18,7 +18,7 @@ select:
> >>    properties:
> >>      compatible:
> >>        contains:
> >> -        pattern: "^atmel,(24(c|cs|mac)[0-9]+|spd)$"
> >> +        pattern: "^atmel,(24(c|cs|mac)[0-9]+[a-z0-9]*|spd)$"
> 
> > Could we relax the pattern instead to make this bloat less? Would it be
> > problematic to just allow "^atmel,(24(c|cs|mac)[a-z0-9]+|spd)$"?
> 
> I) "^atmel,(24(c|cs|mac)[a-z0-9]+|spd)$" :
> The first pattern does not specify where the digits must occur within
> the alphanumeric sequence that follows 24c, 24cs, or 24mac. It allows
> the sequence to be all letters, all digits, or any mix thereof.
> 
> II) "^atmel,(24(c|cs|mac)[0-9]+[a-z0-9]*|spd)$" :
> The second pattern specifically requires that at least one digit appears
> immediately after 24c, 24cs, or 24mac, and only after this digit can
> letters appear.

> As hypothetical example :
> atmel,24cabc would match the first pattern but not the second because
> there are no digits immediately following 24c.
> atmel,24c123 would match both patterns because there are digits
> immediately following 24c, and the first pattern doesn't care about
> the position of the digits within the alphanumeric sequence.
> 
> In case of at24,mac02e4 and at24,mac02e6 match both patterns.
> 
> Let me know your thoughts.

Basically my reasoning here is that both patterns are very permissive
(although one clearly more than the other) and do not stop people from
creating compatibles that do not correspond to a real device, so I felt
that the more complex regex didn't really provide enough benefit
compared to keeping the regex simpler.

> I agree to change the pattern as you suggest.

:+1:



Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)