linux-kernel - Re: Two "bugletts" on SPARC 64 @ kernel 2.4

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20060821.121621.18301975.davem@davemloft.net>
Date:	Mon, 21 Aug 2006 12:16:21 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	DJurzitza@...manbecker.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Two "bugletts" on SPARC 64 @ kernel 2.4

From: "Jurzitza, Dieter" <DJurzitza@...manbecker.com>
Date: Mon, 21 Aug 2006 13:37:51 +0200

> --- linux/include/linux/module.h	2004-12-15 08:34:44.000000000 +0100
> +++ linux/include/linux/module.h	2004-12-15 08:45:32.000000000 +0100
> @@ -31,7 +31,11 @@
>  /* Used by get_kernel_syms, which is obsolete.  */
>  struct kernel_sym
>  {
> -	unsigned long value;
> +#ifdef __ARCH_SPARC64_ATOMIC__
> +	  unsigned int value;
> +#else
> +          unsigned long value;
> +#endif
>  	char name[60];		/* should have been 64-sizeof(long); oh well */
>  };

1) You should post sparc patches at least CC:'d to sparclinux@...r.kernel.org
   which is where the Sparc developers hang out.

2) I can't see any reason why this part of your patch can be valid.
   This structure is exported to userspace and therefor is part of
   the user-visible API and thus cannot be changed.

If there is some bug or bogus limitation in the module tools which
limits the number of symbols visible due to the sizing of this
structure, that is what needs to be changed not this structure.
-
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/