Bug 132063 - LTC19497-CONFIG_BASE_SMALL not defined when PID_MAX_DEFAULT is used
Summary: LTC19497-CONFIG_BASE_SMALL not defined when PID_MAX_DEFAULT is used
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: RC 1
Hardware: i386 Linux
: P5 - None : Normal
Target Milestone: ---
Assignee: Thorsten Kukuk
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-02 20:45 UTC by LTC BugProxy
Modified: 2016-02-13 09:44 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
threads.h (873 bytes, text/plain)
2005-11-02 20:47 UTC, LTC BugProxy
Details
bob16.c (141 bytes, text/plain)
2005-11-02 20:49 UTC, LTC BugProxy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description LTC BugProxy 2005-11-02 20:45:11 UTC
LTC Owner is: thinh@us.ibm.com
LTC Originator is: dgardnr@us.ibm.com


Problem description:
CONFIG_BASE_SMALL not defined when PID_MAX_DEFAULT is used

If this is not an installation problem,
       Provide output from "uname -a", if possible:
Linux bob16 2.6.13-8-default #1 Tue Sep 6 12:59:22 UTC 2005 i686 i686 i386 GNU/Linux
I am running OSS 10 rc1.

Hardware Environment
    Machine type (p650, x235, SF2, etc.):x305
    Cpu type (Power4, Power5, IA-64, etc.):IA-32

Is this reproducible? Yes.
    If so, how long does it (did it) take to reproduce it? 15 sec
    Describe the steps:
Running gcc on the c code that I will attach to the bug.

Additional information:
In OSS 10, PID_MAX_DEFAULT is defined this way in /usr/include/linux/threads.h:
#define PID_MAX_DEFAULT (CONFIG_BASE_SMALL ? 0x1000 : 0x8000)

On SLES 9:
#define PID_MAX_DEFAULT 0x8000

When I compile on OSS 10, I get the error "CONFIG_BASE_SMALL undeclared."
I looked for where CONFIG_BASE_SMALL was defined and could not find any .h that
does this.

Created an attachment (id=13217)
code to create error


Created an attachment (id=13218)
threads.h from my OSS machine


This seems to be one of parameters in the .config file.
Can you check it there?

yes, it is in the .config file. But it is used for building the kernel modules,
not the user space app.

I don't have an OSS10 installed box.
Can I have access to yopurs?

Created mirror request (id=4869)Novell Bugzilla

Please mirror to Novell-SuSE team. Thanks.
Comment 1 LTC BugProxy 2005-11-02 20:47:16 UTC
Created attachment 56288 [details]
threads.h
Comment 2 LTC BugProxy 2005-11-02 20:49:29 UTC
Created attachment 56289 [details]
bob16.c
Comment 3 Olaf Kirch 2005-11-15 11:30:28 UTC
This is a problem with the glibc header files, not the kernel I think.
It's safe to remove the CONFIG_BASE_FULL check from the headers; this
is always false except if you choose CONFIG_EMBEDDED which we don't do
anyway.
Comment 4 Thorsten Kukuk 2005-11-15 11:34:27 UTC
From the test program:
#define _GNU_SOURCE 1
#include <linux/threads.h> 


This test case is invalid. If you include kernel headers directly in userspace programs, you have to take care for this for yourself. In short: Don't do that.