Re: 2.6.20-mm1: PTRACE=y, PROC_FS=n compile error

> This causes the following compile error with CONFIG_PTRACE=y, 
> CONFIG_PROC_FS=n:

Bah.  I moved ptrace_may_attach to fs/proc/base.c so that CONFIG_PTRACE=n
could just omit kernel/ptrace.c entirely and still get the function for
fs/proc/base.c to use (and because that uses it many more times than ptrace
does).  I'd forgotten that procfs could be disabled, since noone ever does.

What do people suggest?  It's not a very big function.


Thanks,
Roland
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: 2.6.20-mm1: PTRACE=y, PROC_FS=n compile error
    • From: Christoph Hellwig <[email protected]>

• References:
  • 2.6.20-mm1: PTRACE=y, PROC_FS=n compile error
    • From: Adrian Bunk <[email protected]>

• Prev by Date: Please pull git390 'for-linus' branch
• Next by Date: PROBLEM: kernel oops 2.6.20 (ubuntu feisty) when inserting compact flash card
• Previous by thread: 2.6.20-mm1: PTRACE=y, PROC_FS=n compile error
• Next by thread: Re: 2.6.20-mm1: PTRACE=y, PROC_FS=n compile error
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]