linux-kernel - Re: build failure in linux-next

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]

Date:	Thu, 1 Mar 2012 22:32:43 +0530
From:	Siddhesh Poyarekar <siddhesh.poyarekar@...il.com>
To:	Mark Salter <msalter@...hat.com>
Cc:	linux-next@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: build failure in linux-next

On Thu, Mar 1, 2012 at 9:41 PM, Mark Salter <msalter@...hat.com> wrote:
> In linux-next, this breaks nommu builds:
>
> commit b8665bd461ecdc561e7c95d039567d0a79208226
> Author: Siddhesh Poyarekar <siddhesh.poyarekar@...il.com>
> Date:   Sat Feb 25 12:28:09 2012 +1100
>
>    procfs: mark thread stack correctly in proc/<pid>/maps
>
> I think this was merged into linux-next from the -mm tree.
>
> There are unbalanced parens in fs/proc/task_nommu.c which leads to this
> when building:
>
> fs/proc/task_nommu.c: In function 'nommu_vma_show':
> fs/proc/task_nommu.c:177:2: warning: no return statement in function returning non-void
> fs/proc/task_nommu.c: At top level:
> fs/proc/task_nommu.c:179:14: error: expected ')' before '\xa'
> fs/proc/task_nommu.c:180:2: error: expected identifier or '(' before 'return'
> fs/proc/task_nommu.c:181:1: error: expected identifier or '(' before '}' token
>

Sorry about that. My latest patch submission to procfs happens to fix this:

https://lkml.org/lkml/2012/3/1/4

Do you need a separate submission that fixes just this build failure?


-- 
Siddhesh Poyarekar
http://siddhesh.in
--
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/