* [PATCH] fs : mark nibblemap const
@ 2007-07-13 10:26 Philippe De Muyter
2007-09-02 19:40 ` Hint needed : how to debug sempahore's problem Philippe De Muyter
0 siblings, 1 reply; 3+ messages in thread
From: Philippe De Muyter @ 2007-07-13 10:26 UTC (permalink / raw)
To: linux-kernel
Hi all
Mark nibblemap const
Signed-off-by: Philippe De Muyter <phdm@macqel.be>
diff -r 6c0a10cc415a fs/affs/bitmap.c
--- a/fs/affs/bitmap.c Thu Jul 5 16:10:16 2007 -0700
+++ b/fs/affs/bitmap.c Fri Jul 13 12:21:14 2007 +0200
@@ -11,7 +11,7 @@
/* This is, of course, shamelessly stolen from fs/minix */
-static int nibblemap[] = { 0,1,1,2,1,2,2,3,1,2,2,3,2,3,3,4 };
+static const int nibblemap[] = { 0,1,1,2,1,2,2,3,1,2,2,3,2,3,3,4 };
static u32
affs_count_free_bits(u32 blocksize, const void *data)
diff -r 6c0a10cc415a fs/ext2/balloc.c
--- a/fs/ext2/balloc.c Thu Jul 5 16:10:16 2007 -0700
+++ b/fs/ext2/balloc.c Fri Jul 13 12:21:14 2007 +0200
@@ -522,7 +522,7 @@ io_error:
#ifdef EXT2FS_DEBUG
-static int nibblemap[] = {4, 3, 3, 2, 3, 2, 2, 1, 3, 2, 2, 1, 2, 1, 1, 0};
+static const int nibblemap[] = {4, 3, 3, 2, 3, 2, 2, 1, 3, 2, 2, 1, 2, 1, 1, 0};
unsigned long ext2_count_free (struct buffer_head * map, unsigned int numchars)
{
diff -r 6c0a10cc415a fs/ext3/bitmap.c
--- a/fs/ext3/bitmap.c Thu Jul 5 16:10:16 2007 -0700
+++ b/fs/ext3/bitmap.c Fri Jul 13 12:21:14 2007 +0200
@@ -13,7 +13,7 @@
#ifdef EXT3FS_DEBUG
-static int nibblemap[] = {4, 3, 3, 2, 3, 2, 2, 1, 3, 2, 2, 1, 2, 1, 1, 0};
+static const int nibblemap[] = {4, 3, 3, 2, 3, 2, 2, 1, 3, 2, 2, 1, 2, 1, 1, 0};
unsigned long ext3_count_free (struct buffer_head * map, unsigned int numchars)
{
diff -r 6c0a10cc415a fs/ext4/bitmap.c
--- a/fs/ext4/bitmap.c Thu Jul 5 16:10:16 2007 -0700
+++ b/fs/ext4/bitmap.c Fri Jul 13 12:21:14 2007 +0200
@@ -13,7 +13,7 @@
#ifdef EXT4FS_DEBUG
-static int nibblemap[] = {4, 3, 3, 2, 3, 2, 2, 1, 3, 2, 2, 1, 2, 1, 1, 0};
+static const int nibblemap[] = {4, 3, 3, 2, 3, 2, 2, 1, 3, 2, 2, 1, 2, 1, 1, 0};
unsigned long ext4_count_free (struct buffer_head * map, unsigned int numchars)
{
diff -r 6c0a10cc415a fs/minix/bitmap.c
--- a/fs/minix/bitmap.c Thu Jul 5 16:10:16 2007 -0700
+++ b/fs/minix/bitmap.c Fri Jul 13 12:21:14 2007 +0200
@@ -17,7 +17,7 @@
#include <linux/bitops.h>
#include <linux/sched.h>
-static int nibblemap[] = { 4,3,3,2,3,2,2,1,3,2,2,1,2,1,1,0 };
+static const int nibblemap[] = { 4,3,3,2,3,2,2,1,3,2,2,1,2,1,1,0 };
static unsigned long count_free(struct buffer_head *map[], unsigned numblocks, __u32 numbits)
{
^ permalink raw reply [flat|nested] 3+ messages in thread
* Hint needed : how to debug sempahore's problem
2007-07-13 10:26 [PATCH] fs : mark nibblemap const Philippe De Muyter
@ 2007-09-02 19:40 ` Philippe De Muyter
2007-09-02 19:47 ` Alexander Shishkin
0 siblings, 1 reply; 3+ messages in thread
From: Philippe De Muyter @ 2007-09-02 19:40 UTC (permalink / raw)
To: linux-kernel; +Cc: uclinux-dev
Hi all,
Can someone give me some hint or link for the following question :
I have several processes blocked in 'D' state, and I surmise they are
waiting for a semaphore (in the `down' routine). How is it possible :
- to verify the processes are really blocked on a semaphore,
- to see which semaphore they are waiting on,
- to find out which process/driver/whatever holds those semaphores.
If that matters, I work on a m68k board.
Thanks in advance
Philippe
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Hint needed : how to debug sempahore's problem
2007-09-02 19:40 ` Hint needed : how to debug sempahore's problem Philippe De Muyter
@ 2007-09-02 19:47 ` Alexander Shishkin
0 siblings, 0 replies; 3+ messages in thread
From: Alexander Shishkin @ 2007-09-02 19:47 UTC (permalink / raw)
To: Philippe De Muyter; +Cc: linux-kernel, uclinux-dev
On 9/2/07, Philippe De Muyter <phdm@macqel.be> wrote:
> Hi all,
Hi,
> Can someone give me some hint or link for the following question :
>
> I have several processes blocked in 'D' state, and I surmise they are
> waiting for a semaphore (in the `down' routine). How is it possible :
> - to verify the processes are really blocked on a semaphore,
> - to see which semaphore they are waiting on,
> - to find out which process/driver/whatever holds those semaphores.
I'm sure there might be a better solution, but the easiest one I've
found for myself is enabling sysrq and sending sysrq-p or sysrq-t
combination to the board's console and see the callpaths that lead to
a deadlock (or other incorrect locking situation) in the kernel.
--
I like long walks, especially when they are taken by people who annoy me.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-09-02 19:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-07-13 10:26 [PATCH] fs : mark nibblemap const Philippe De Muyter
2007-09-02 19:40 ` Hint needed : how to debug sempahore's problem Philippe De Muyter
2007-09-02 19:47 ` Alexander Shishkin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®