From: Len Brown <len.brown@intel.com>
To: Auke Kok <sofar@lunar-linux.org>
Cc: linux-kernel@vger.kernel.org, dev@grsecurity.net,
lunar-dev@lunar-linux.org
Subject: Re: 2x procfs bug with 2.4.23
Date: 16 Dec 2003 03:08:47 -0500 [thread overview]
Message-ID: <1071562126.2443.101.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE001B5726C@hdsmsx402.hd.intel.com>
Auke,
Problem #2 should be fixed by the patch here:
http://bugzilla.kernel.org/show_bug.cgi?id=991
Please let me know if it works for you.
thanks,
-Len
On Sun, 2003-12-14 at 18:51, Auke Kok wrote:
> Hi,
>
> I have encountered 2 different procfs bugs with 2.4.23, where procfs
> seems to be running a possible race, the other with ACPI subdirs being
> created in /proc instead of /proc/acpi, possibly leading to more
> problems.
>
> both kernels run the official grsec patchset, so I forward them to
>
> 1) procfs sys shows alternatingly up as "file", "socket", and
> "directory"
>
> root@server /proc # ls -ld sys
> srwxrwxrwx 10 root root 0 2003-12-15 00:38 sys
> root@server /proc # ls -ld sys
> -r--r--r-- 10 root root 0 2003-12-15 00:38 sys
> root@server /proc # ls -ld sys
> prw------- 10 root root 0 2003-12-15 00:41 sys
> root@server /proc # ls -ld sys
> prw------- 10 root root 0 2003-12-15 00:41 sys
> root@server /proc # ls -ld sys
> srwxrwxrwx 10 root root 0 2003-12-15 00:41 sys
> root@server /proc # cd sys
> root@server /proc/sys # ls -ld .
> srwxrwxrwx 10 root root 0 2003-12-15 00:41 .
> root@server /proc/sys # pwd
> /proc/sys
> root@server /proc/sys # ls
> abi debug dev fs kernel net proc vm
>
> etc... very very annoying since this box needs ip_forward enabled
> after
> boot to function!
>
> The other box has an unsupported ACPI core:
>
> [from dmesg]
> ACPI: Unable to locate RSDP
> ACPI: Subsystem revision 20031002
> PCI: PCI BIOS revision 2.10 entry at 0xf7ec0, last bus=0
> PCI: Using configuration type 1
> ACPI: System description tables not found
> ACPI-0084: *** Error: acpi_load_tables: Could not get RSDP,
> AE_NOT_FOUND
> ACPI-0134: *** Error: acpi_load_tables: Could not load tables:
> AE_NOT_FOUND
> ACPI: Unable to load the System Description Tables
> PCI: Probing PCI hardware
> PCI: ACPI tables contain no PCI IRQ routing entries
>
> it's a genuine pII-mmx, so I don't care about the ACPI. However, the
> /proc/acpi directory isn't created but the subdirs for enabled
> components are, which could result in confusion/problems:
>
> ~ # ls -dF /proc/[a-zA-Z_-]*
> /proc/ac_adapter/ /proc/interrupts /proc/partitions
> /proc/battery/ /proc/iomem /proc/pci
> /proc/bus/ /proc/ioports /proc/processor/
> /proc/button/ /proc/irq/ /proc/self@
> /proc/cmdline /proc/kmsg /proc/slabinfo
> /proc/cpuinfo /proc/ksyms /proc/stat
> /proc/crypto /proc/loadavg /proc/swaps
> /proc/devices /proc/locks /proc/sys/
> /proc/dma /proc/lvm/ /proc/sysvipc/
> /proc/driver/ /proc/mdstat /proc/thermal_zone/
> /proc/execdomains /proc/meminfo /proc/tty/
> /proc/fan/ /proc/misc /proc/uptime
> /proc/filesystems /proc/modules /proc/version
> /proc/fs/ /proc/mounts@
> /proc/ide/ /proc/net/
>
> [note the thermal_zone... it should not be there I think ;^)]
>
>
> -- not subscribed, reply to sofar <at> lunar.linux <dot> org
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next parent reply other threads:[~2003-12-16 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE001B5726C@hdsmsx402.hd.intel.com>
2003-12-16 8:08 ` Len Brown [this message]
2003-12-14 23:51 2x procfs bug with 2.4.23 Auke Kok
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1071562126.2443.101.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=dev@grsecurity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lunar-dev@lunar-linux.org \
--cc=sofar@lunar-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.