From: Alex Buell <alex.buell@munted.org.uk>
To: sparclinux@vger.kernel.org
Subject: Re: silo fails to build with e2fsprogs-1.41.14 (undefined
Date: Mon, 17 Jan 2011 13:22:38 +0000 [thread overview]
Message-ID: <1295270558.15315.17.camel@lithium> (raw)
In-Reply-To: <4D2B59AC.8040203@gentoo.org>
On Sun, 2011-01-16 at 19:59 -0800, David Miller wrote:
> From: Alex Buell <alex.buell@munted.org.uk>
> Date: Sat, 15 Jan 2011 12:57:09 +0000
>
> > On Sat, 2011-01-15 at 13:07 +0100, Raúl Porcel wrote:
> >> Thanks, it builds, but silo fails to work:
> >>
> >> Boot device: disk1 File and args:
> >> SILO Version 1.4.14_git2010228_p1
> >>
> >> Unknown ext2 error: 4294967295
> >>
> >> Fatal error: Unable to open filesystem
> >>
> >> Couldn't load /etc/silo.conf
> >> No config file loaded, you can boot just from this command line
> >> Type [prompath;]part/path_to_image [parameters] on the prompt
> >> E.g. /iommu/sbus/espdma/esp/sd@3,0;4/vmlinux root=/dev/sda4
> >> or 2/vmlinux.live (to load vmlinux.live from 2nd partition of boot disk)
> >> boot:
> >
> > This problem exists with all versions of silo linked against
> > e2fsprogs-1.41.14.
>
> Can you guys please test this patch out? It's against the current
> tree.
>
> Thanks!
>
> --------------------
> malloc: Provide posix_memalign() implementation.
>
> ext2progs library really wants a working version of this,
> and thankfully it's not that hard to do.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> diff --git a/common/malloc.c b/common/malloc.c
> index cc3946d..d05061b 100644
> --- a/common/malloc.c
> +++ b/common/malloc.c
> @@ -27,6 +27,12 @@ static char *malloc_ptr = (char *) MALLOC_BASE;
>
> static char *last_alloc = 0;
>
> +static char *align_ptr_to(char *ptr, unsigned long align)
> +{
> + return (char *) ((((unsigned long) ptr) + (align - 1UL)) &
> + ~(align - 1UL));
> +}
> +
> void *malloc (int size)
> {
> char *caddr;
> @@ -34,10 +40,34 @@ void *malloc (int size)
> caddr = malloc_ptr;
> malloc_ptr += size;
> last_alloc = caddr;
> - malloc_ptr = (char *) ((((unsigned long) malloc_ptr) + 7) & (~7));
> + malloc_ptr = align_ptr_to(malloc_ptr, 7UL);
> return caddr;
> }
>
> +int posix_memalign(void **memptr, unsigned long alignment, unsigned long size)
> +{
> + char *caddr;
> +
> + if (alignment & (alignment - 1UL))
> + return -1;
> + if (alignment & (sizeof(void *) - 1UL))
> + return -1;
> +
> + if (size = 0) {
> + *memptr = (void *) 0;
> + return 0;
> + }
> +
> + caddr = align_ptr_to(malloc_ptr, alignment);
> + malloc_ptr = (caddr + size);
> + last_alloc = caddr;
> + malloc_ptr = align_ptr_to(malloc_ptr, 7UL);
> +
> + *memptr = caddr;
> +
> + return 0;
> +}
> +
> void free (void *m)
> {
> if (m = last_alloc)
> diff --git a/second/fs/ext2.c b/second/fs/ext2.c
> index 12d00dc..57f5e9a 100644
> --- a/second/fs/ext2.c
> +++ b/second/fs/ext2.c
> @@ -163,9 +163,3 @@ void *realloc(void *p, int size)
> {
> return NULL;
> }
> -
> -int posix_memalign(void **memptr, size_t alignment, size_t size)
> -{
> - *memptr = NULL;
> - return -1;
> -}
With that patch, I now get a different error:
SILO Version 1.4.14
ERROR: Last trap: Memory Address not aligned
Error -256
{0] OK
(Now I've got to boot off my rescue CD and rebuild SILO)
Is anyone else getting the same error?
--
Tactical Nuclear Kittens
next prev parent reply other threads:[~2011-01-17 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 19:10 silo fails to build with e2fsprogs-1.41.14 (undefined references Raúl Porcel
2011-01-10 19:29 ` silo fails to build with e2fsprogs-1.41.14 (undefined David Miller
2011-01-15 12:07 ` silo fails to build with e2fsprogs-1.41.14 (undefined references Raúl Porcel
2011-01-15 12:57 ` silo fails to build with e2fsprogs-1.41.14 (undefined Alex Buell
2011-01-16 5:06 ` David Miller
2011-01-17 3:59 ` David Miller
2011-01-17 4:03 ` Alex Buell
2011-01-17 13:22 ` Alex Buell [this message]
2011-01-17 17:02 ` silo fails to build with e2fsprogs-1.41.14 (undefined references Richard Mortimer
2011-01-17 17:23 ` silo fails to build with e2fsprogs-1.41.14 (undefined Alex Buell
2011-01-17 17:35 ` Alex Buell
2011-01-17 21:12 ` David Miller
2011-01-17 21:14 ` David Miller
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=1295270558.15315.17.camel@lithium \
--to=alex.buell@munted.org.uk \
--cc=sparclinux@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.