[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201002220128.21067.bzolnier@gmail.com>
Date: Mon, 22 Feb 2010 01:28:20 +0100
From: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To: David Miller <davem@...emloft.net>
Cc: rob@...dley.net, qemu-devel@...gnu.org, blauwirbel@...il.com,
pbonzini@...hat.com, atar4qemu@...glemail.com,
linux-kernel@...r.kernel.org, sam@...nborg.org
Subject: Re: Commit 085219f79cad broke Sparc-32 back in 2.6.28.
On Monday 22 February 2010 12:57:19 am David Miller wrote:
> From: Rob Landley <rob@...dley.net>
> Date: Sun, 21 Feb 2010 10:25:09 -0600
>
> > 085219f79cad89291699bd2bfb21c9fdabafe65f is first bad commit
> > commit 085219f79cad89291699bd2bfb21c9fdabafe65f
> > Author: Sam Ravnborg <sam@...nborg.org>
> > Date: Fri Jan 2 18:47:34 2009 -0800
> >
> > sparc32: use proper types in struct stat
> >
> > Like sparc64 use proper types in struct stat
> >
> > Signed-off-by: Sam Ravnborg <sam@...nborg.org>
> > Signed-off-by: David S. Miller <davem@...emloft.net>
> >
> > This commit breaks stat and makes sparc32 essentially unusable. It changes
> > the size of the various types in stat.h, and means that if you "mount -t tmpfs
> > /tmp /tmp" and then try to ls /tmp, ls dies with a memory allocation error.
> >
> > I've confirmed that reverting it fixes the problem.
>
> Thanks for tracking this down Rob, I'll work on a fix and
> push it around.
Looking at how whole sparc32 has been apparently broken for over a year now
because of a purely cleanup patch I wonder if it would be appropriate to
make sparc32 into 'legacy only' and provide 'a stability promise' for it?
Just an idea.. ;)
--
Bartlomiej Zolnierkiewicz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists