[linux-yocto] [PATCH v2] ti81xx: Fix buffer overflow error in sysfs pin-mux interface.

[Denys Dmytriyenko]

On Thu, Jul 18, 2013 at 08:11:45AM -0400, Bruce Ashfield wrote:
> On 13-07-18 2:14 AM, Graeme Smecher wrote:
> >Hi Bruce,
> >
> >On 17/07/13 10:22 PM, Bruce Ashfield wrote:
> >>On 13-07-17 11:08 AM, Graeme Smecher wrote:
> >>>This bug was introduced in commit
> >>>d00bf72d119d98b2a19b48b2eebdc8b5b657284d.
> >>>The declaration of the "mode" variable didn't reserve enough space
> >>>for ti816x
> >>>or ti814x strings. The result was corruption when displaying files in
> >>>/sys/kernel/debug/omap_mux.
> >>
> >>This looks to be broken in all the mainline kernels that I checked from
> >>3.4 -> 3.11-rc.
> >>
> >>Which kernel version in particular did you test it with ? That'll guide
> >>where I apply it.
> >>
> >>Are there plans to upstream the change, or is it already staged in a TI
> >>tree, or arm repo ?
> >
> >Sorry -- this applies to the arago-project linux-omap3 tree:
> 
> Aha!
> 
> >
> >git://arago-project.org/git/projects/linux-omap3.git
> >http://arago-project.org/git/projects/linux-omap3.git
> >
> >The arago-project site doesn't appear to host its own mailing lists
> >(though it does contain links to yocto lists.) I'm having a hard time
> >tracking down the right mailing list for this patch, and others like it.
> 
> In that case, I've added Denys Dmytriyenko who can likely advise on the
> right list to use.

All I can suggest is to ask a question on e2e.ti.com forums - there's no 
dedicated mailing list for kernel questions on ti81x platform...


> I obviously don't mind taking the patch (or patches) and carrying them
> as well, but without the rest of the board support .. it would be less
> than effective :)

I would agree - forward-porting the entire board support for ti81x would not 
be trivial and it was only done for 2.6.37.

-- 
Denys