| To: | Brian Foster <bfoster@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH RFC] fs: xfs: Fix xfs_trans_read_buf event tracing |
| From: | Pratyush Anand <panand@xxxxxxxxxx> |
| Date: | Thu, 19 Feb 2015 22:55:43 +0530 |
| Cc: | david@xxxxxxxxxxxxx, xfs@xxxxxxxxxxx, jbastian@xxxxxxxxxx, ddutile@xxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20150219172028.GC2291@xxxxxxxxxxxxxx> |
| References: | <7fb3278485ca5d8b48cd1ba980be6cc11dafc11b.1424352124.git.panand@xxxxxxxxxx> <20150219172028.GC2291@xxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 |
On Thursday 19 February 2015 10:50 PM, Brian Foster wrote: On Thu, Feb 19, 2015 at 06:54:33PM +0530, Pratyush Anand wrote:My root file system is xfs. As soon as I enable event for xfs_trans_read_buf `echo xfs:xfs_trans_read_buf >> /sys/kernel/debug/tracing/set_event`, I see a kernel panic. A little bit of debugging shows that bp->b_fspriv is NULL many a time when trace_xfs_trans_read_buf(bp->b_fspriv) is called. I do not have any idea about xfs filesystem. So, I am not sure, if it is expected to have bp->b_fspriv = NULL at this location. This patch fixes the issue, until we have a better fix. Signed-off-by: Pratyush Anand <panand@xxxxxxxxxx> ---A fix for this has been posted here: http://oss.sgi.com/archives/xfs/2015-02/msg00101.html Thanks Brian ~Pratyush |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH RFC] fs: xfs: Fix xfs_trans_read_buf event tracing, Brian Foster |
|---|---|
| Next by Date: | [PATCH v5 01/18] xfs: create individual inode alloc. helper, Brian Foster |
| Previous by Thread: | Re: [PATCH RFC] fs: xfs: Fix xfs_trans_read_buf event tracing, Brian Foster |
| Next by Thread: | Re: [PATCH RFC] fs: xfs: Fix xfs_trans_read_buf event tracing, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |