linux-kernel - Re: [PATCH 00/32] Blackfin update for 2.6.22-rc2

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070521143730.GA18110@linux-sh.org>
Date:	Mon, 21 May 2007 23:37:30 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Robin Getz <rgetz@...ckfin.uclinux.org>
Cc:	Bryan Wu <bryan.wu@...log.com>, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/32] Blackfin update for 2.6.22-rc2

On Mon, May 21, 2007 at 10:35:08AM -0400, Robin Getz wrote:
> On Mon 21 May 2007 06:09, Bryan Wu pondered:
> > Lots of update for 2.6.22-rc2 and tested on STAMP537 board.
> >
> 
> One of the things I noticed when trying out 2.6.22-rc1, on blackfin was:
> 
>  CALL    scripts/checksyscalls.sh
[snip syscalls]
> 
> since there is noMMU, are we better:
>  - putting stubs (return ENOSYS - give runtime errors), or 
>  - just ignore the errors - and give compile errors? (Is there any way to put 
> something into the syscall table, as not to get the warnings?)
> 
No, you'd be better of figuring out which ones you can support and which
ones you have to -ENOSYS. CONFIG_MMU=n is not a "get out of syscalls
free" card. Many of these have no dependency on CONFIG_MMU, anyways.
-
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/