public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] xfs: more info from kmem deadlocks and high-level error msgs
@ 2015-10-10  3:24 Eric Sandeen
  2015-10-15  9:50 ` Carlos Maiolino
  0 siblings, 1 reply; 2+ messages in thread
From: Eric Sandeen @ 2015-10-10  3:24 UTC (permalink / raw)
  To: xfs

In an effort to get more useful out of "possible memory
allocation deadlock" messages, print the size of the
requested allocation, and dump the stack if the xfs error
level is tuned high.

The stack dump is implemented in define_xfs_printk_level()
for error levels >= LOGLEVEL_ERR, partly because it
seems generically useful, and also because kmem.c has
no knowledge of xfs error level tunables or other such bits,
it's very kmem-specific.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---

diff --git a/fs/xfs/kmem.c b/fs/xfs/kmem.c
index a7a3a63..dfe3a8b 100644
--- a/fs/xfs/kmem.c
+++ b/fs/xfs/kmem.c
@@ -55,8 +55,8 @@ kmem_alloc(size_t size, xfs_km_flags_t flags)
 			return ptr;
 		if (!(++retries % 100))
 			xfs_err(NULL,
-		"possible memory allocation deadlock in %s (mode:0x%x)",
-					__func__, lflags);
+		"possible memory allocation deadlock size %u in %s (mode:0x%x)",
+					(unsigned int)size, __func__, lflags);
 		congestion_wait(BLK_RW_ASYNC, HZ/50);
 	} while (1);
 }
diff --git a/fs/xfs/xfs_message.c b/fs/xfs/xfs_message.c
index d8b6754..11792d8 100644
--- a/fs/xfs/xfs_message.c
+++ b/fs/xfs/xfs_message.c
@@ -17,6 +17,7 @@
 
 #include "xfs.h"
 #include "xfs_fs.h"
+#include "xfs_error.h"
 #include "xfs_format.h"
 #include "xfs_log_format.h"
 #include "xfs_trans_resv.h"
@@ -43,6 +44,7 @@ void func(const struct xfs_mount *mp, const char *fmt, ...)	\
 {								\
 	struct va_format	vaf;				\
 	va_list			args;				\
+	int			level;				\
 								\
 	va_start(args, fmt);					\
 								\
@@ -51,6 +53,11 @@ void func(const struct xfs_mount *mp, const char *fmt, ...)	\
 								\
 	__xfs_printk(kern_level, mp, &vaf);			\
 	va_end(args);						\
+								\
+	if (!kstrtoint(kern_level, 0, &level) &&		\
+	    level <= LOGLEVEL_ERR &&				\
+	    xfs_error_level >= XFS_ERRLEVEL_HIGH)		\
+		xfs_stack_trace();				\
 }								\
 
 define_xfs_printk_level(xfs_emerg, KERN_EMERG);

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] xfs: more info from kmem deadlocks and high-level error msgs
  2015-10-10  3:24 [PATCH] xfs: more info from kmem deadlocks and high-level error msgs Eric Sandeen
@ 2015-10-15  9:50 ` Carlos Maiolino
  0 siblings, 0 replies; 2+ messages in thread
From: Carlos Maiolino @ 2015-10-15  9:50 UTC (permalink / raw)
  To: Eric Sandeen; +Cc: xfs

On Fri, Oct 09, 2015 at 10:24:37PM -0500, Eric Sandeen wrote:
> In an effort to get more useful out of "possible memory
> allocation deadlock" messages, print the size of the
> requested allocation, and dump the stack if the xfs error
> level is tuned high.
> 
> The stack dump is implemented in define_xfs_printk_level()
> for error levels >= LOGLEVEL_ERR, partly because it
> seems generically useful, and also because kmem.c has
> no knowledge of xfs error level tunables or other such bits,
> it's very kmem-specific.
> 
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>

Looks good to me:

Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
> 
> diff --git a/fs/xfs/kmem.c b/fs/xfs/kmem.c
> index a7a3a63..dfe3a8b 100644
> --- a/fs/xfs/kmem.c
> +++ b/fs/xfs/kmem.c
> @@ -55,8 +55,8 @@ kmem_alloc(size_t size, xfs_km_flags_t flags)
>  			return ptr;
>  		if (!(++retries % 100))
>  			xfs_err(NULL,
> -		"possible memory allocation deadlock in %s (mode:0x%x)",
> -					__func__, lflags);
> +		"possible memory allocation deadlock size %u in %s (mode:0x%x)",
> +					(unsigned int)size, __func__, lflags);
>  		congestion_wait(BLK_RW_ASYNC, HZ/50);
>  	} while (1);
>  }
> diff --git a/fs/xfs/xfs_message.c b/fs/xfs/xfs_message.c
> index d8b6754..11792d8 100644
> --- a/fs/xfs/xfs_message.c
> +++ b/fs/xfs/xfs_message.c
> @@ -17,6 +17,7 @@
>  
>  #include "xfs.h"
>  #include "xfs_fs.h"
> +#include "xfs_error.h"
>  #include "xfs_format.h"
>  #include "xfs_log_format.h"
>  #include "xfs_trans_resv.h"
> @@ -43,6 +44,7 @@ void func(const struct xfs_mount *mp, const char *fmt, ...)	\
>  {								\
>  	struct va_format	vaf;				\
>  	va_list			args;				\
> +	int			level;				\
>  								\
>  	va_start(args, fmt);					\
>  								\
> @@ -51,6 +53,11 @@ void func(const struct xfs_mount *mp, const char *fmt, ...)	\
>  								\
>  	__xfs_printk(kern_level, mp, &vaf);			\
>  	va_end(args);						\
> +								\
> +	if (!kstrtoint(kern_level, 0, &level) &&		\
> +	    level <= LOGLEVEL_ERR &&				\
> +	    xfs_error_level >= XFS_ERRLEVEL_HIGH)		\
> +		xfs_stack_trace();				\
>  }								\
>  
>  define_xfs_printk_level(xfs_emerg, KERN_EMERG);
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

-- 
Carlos

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-10-15  9:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-10  3:24 [PATCH] xfs: more info from kmem deadlocks and high-level error msgs Eric Sandeen
2015-10-15  9:50 ` Carlos Maiolino

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox