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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 3 Dec 2020 15:47:18 +0000
From:   Madalin Bucur <>
To:     Patrick Havelange <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,
        "" <>,
        "" <>
Subject: RE: [PATCH net 1/4] net: freescale/fman: Split the main resource
 region reservation

> -----Original Message-----
> From: Patrick Havelange <>
> Sent: 03 December 2020 15:51
> To: Madalin Bucur <>; David S. Miller
> <>; Jakub Kicinski <>;
> Cc: Patrick Havelange <>
> Subject: [PATCH net 1/4] net: freescale/fman: Split the main resource
> region reservation
> The main fman driver is only using some parts of the fman memory
> region.
> Split the reservation of the main region in 2, so that the other
> regions that will be used by fman-port and fman-mac drivers can
> be reserved properly and not be in conflict with the main fman
> reservation.
> Signed-off-by: Patrick Havelange <>

I think the problem you are trying to work on here is that the device
tree entry that describes the FMan IP allots to the parent FMan device the
whole memory-mapped registers area, as described in the device datasheet.
The smaller FMan building blocks (ports, MDIO controllers, etc.) are
each using a nested subset of this memory-mapped registers area.
While this hierarchical depiction of the hardware has not posed a problem
to date, it is possible to cause issues if both the FMan driver and any
of the sub-blocks drivers are trying to exclusively reserve the registers
area. I'm assuming this is the problem you are trying to address here,
besides the stack corruption issue. While for the latter I think we can
put together a quick fix, for the former I'd like to take a bit of time
to select the best fix, if one is really needed. So, please, let's split
the two problems and first address the incorrect stack memory use.


Powered by blists - more mailing lists