public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Georg Schild <dangertools@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc[2|3] protection fault on /proc/devices
Date: Tue, 07 Dec 2004 08:50:15 +0100	[thread overview]
Message-ID: <41B560B7.9080300@gmx.net> (raw)
In-Reply-To: <20041206234044.51667e94.akpm@osdl.org>

Andrew Morton wrote:
> Georg Schild <dangertools@gmx.net> wrote:
> 
>>Since 2.6.10-rc2 I am having problems accessing /proc/devices. On 
>>startup some init-skripts access this node and print out a protection 
>>fault. i am having this on pcmcia and swap startup. My system is an 
>>amd64 @3000+ in an Acer Aspire 1501Lmi at 64bit mode running gentoo. 
>>.config is the same as on 2.6.10-rc1 which works good. cat on 
>>/proc/devices gives the same problems. The kernel has just a patch for 
>>wbsd (builtin mmc-cardreader) from Pierre Ossman in use, everything else 
>>is vanilla. Does anyone know of this issue and perhaps on how to solve this?
>>
>>Regards
>>
>>Georg Schild
>>
>>
> 
> 
> How odd.  All I can think is that something has registered a zillion
> devices and get_blkdev_list() has run off the /proc page.  But then, it
> should have oopsed in sprintf()..
> 
> Still.  Please send a copy of your /proc/devices from 2.6.10-rc1 and also
> apply this:
> 
> --- 25/drivers/block/genhd.c~a	2004-12-06 23:31:13.677476528 -0800
> +++ 25-akpm/drivers/block/genhd.c	2004-12-06 23:31:30.539913048 -0800
> @@ -48,9 +48,11 @@ int get_blkdev_list(char *p)
>  
>  	down_read(&block_subsys.rwsem);
>  	for (i = 0; i < ARRAY_SIZE(major_names); i++) {
> -		for (n = major_names[i]; n; n = n->next)
> -			len += sprintf(p+len, "%3d %s\n",
> +		for (n = major_names[i]; n; n = n->next) {
> +			if (len < PAGE_SIZE / 2)
> +				len += sprintf(p+len, "%3d %s\n",
>  				       n->major, n->name);
> +		}
>  	}
>  	up_read(&block_subsys.rwsem);
>  
> _
> 
> to 2.6.10-rc3 and see if that fixes it.  If so, please send the
> /proc/devices content from this kernel.
> 
> Beyond that, perhaps something scribbled on the data structures in there. 
> Setting CONFIG_SLAB_DEBUG and/or CONFIG_DEBUG_PAGEALLOC might turn
> something up.

Okay, here the output of /proc/devices on 2.6.10-rc1. I will apply the 
patch and see if it works.

regards

Georg Schild

> Character devices:
>   1 mem
>   2 pty
>   3 ttyp
>   4 /dev/vc/0
>   4 tty
>   4 ttyS
>   5 /dev/tty
>   5 /dev/console
>   5 /dev/ptmx
>   6 lp
>   7 vcs
>  10 misc
>  13 input
>  14 sound
>  21 sg
>  29 fb
>  81 video4linux
>  89 i2c
> 116 alsa
> 128 ptm
> 136 pts
> 161 ircomm
> 162 raw
> 171 ieee1394
> 180 usb
> 202 cpu/msr
> 203 cpu/cpuid
> 216 rfcomm
> 253 devfs
> 254 pcmcia
> 
> Block devices:
>   2 fd
>   3 ide0
>   7 loop
>   8 sd
>  11 sr
>  22 ide1
>  43 nbd
>  65 sd
>  66 sd
>  67 sd
>  68 sd
>  69 sd
>  70 sd
>  71 sd
>  80 i2o_block
> 125 ub
> 128 sd
> 129 sd
> 130 sd
> 131 sd
> 132 sd
> 133 sd
> 134 sd
> 135 sd
> 254 mmc


  reply	other threads:[~2004-12-07  7:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 23:11 2.6.10-rc[2|3] protection fault on /proc/devices Georg Schild
2004-12-07  7:40 ` Andrew Morton
2004-12-07  7:50   ` Georg Schild [this message]
2004-12-07  8:31   ` Georg Schild
2004-12-07  9:05     ` Andrew Morton
2004-12-07  9:02   ` Georg Schild
2004-12-07 15:29   ` George Alexandru Dragoi

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=41B560B7.9080300@gmx.net \
    --to=dangertools@gmx.net \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox