From: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
To: Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: Linux 2.6.24-rc7: sparc64: WARNING: at kernel/lockdep_proc.c:267 lockdep_stats_show()
Date: Wed, 9 Jan 2008 17:31:15 +0100
User-Agent: KMail/1.9.7
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
       David Miller <davem@davemloft.net>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       sparclinux@vger.kernel.org
References: <alpine.LFD.1.00.0801061410290.3148@woody.linux-foundation.org> <200801082339.13198.m.kozlowski@tuxland.pl> <4783FD17.90806@oracle.com>
In-Reply-To: <4783FD17.90806@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200801091731.16043.m.kozlowski@tuxland.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 774
Lines: 29

Hello,

> >>> 	Got this when doing usual looping over /proc entries on fresh test kernel:
> >> What is the usual looping, please?
> > 
> > #!/bin/bash
> > 
> > for i in `find /proc -type f`; do
> >         echo -n "cat $i > /dev/null ... ";
> >         ( cat $i > /dev/null & );
> >         echo "done";
> > done
> 
> OK, thanks.  Probably not related to the problem report, but
> the script should probably check each file for 'readable' (-r).
> /proc/sysrq-trigger is write-only...

Hm... true. Good hint.

Thanks,

	Mariusz


--
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/