public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Dutile <ddutile@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>,
	Pratyush Anand <panand@redhat.com>,
	david@fromorbit.com, xfs@oss.sgi.com
Cc: jbastian@redhat.com
Subject: Re: [PATCH RFC] fs: xfs: Fix xfs_trans_read_buf event tracing
Date: Thu, 19 Feb 2015 17:32:23 -0500	[thread overview]
Message-ID: <54E66477.5060600@redhat.com> (raw)
In-Reply-To: <54E611BA.7010806@sandeen.net>

On 02/19/2015 11:39 AM, Eric Sandeen wrote:
> On 2/19/15 7:24 AM, 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.
>
> What kernel did you hit this on?  What did the backtrace look like?
>
> I've been unable to reproduce the problem so far.
>
> Thanks,
> -Eric
>
RHELSA snap7 kernel (that's RHEL Server for ARM; 3.19-based).

Thanks for everyone's attention. Pratyush has provided a link
to the upstream patch, that we have to pull into our kernel.


>> Signed-off-by: Pratyush Anand <panand@redhat.com>
>> ---
>>   fs/xfs/xfs_trans_buf.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/xfs/xfs_trans_buf.c b/fs/xfs/xfs_trans_buf.c
>> index 0a4d4ab6d9a9..0b67a20643bf 100644
>> --- a/fs/xfs/xfs_trans_buf.c
>> +++ b/fs/xfs/xfs_trans_buf.c
>> @@ -329,7 +329,8 @@ xfs_trans_read_buf_map(
>>
>>   	if (tp)
>>   		_xfs_trans_bjoin(tp, bp, 1);
>> -	trace_xfs_trans_read_buf(bp->b_fspriv);
>> +	if (bp->b_fspriv)
>> +		trace_xfs_trans_read_buf(bp->b_fspriv);
>>   	*bpp = bp;
>>   	return 0;
>>
>>
>

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

  reply	other threads:[~2015-02-19 22:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 13:24 [PATCH RFC] fs: xfs: Fix xfs_trans_read_buf event tracing Pratyush Anand
2015-02-19 16:39 ` Eric Sandeen
2015-02-19 22:32   ` Don Dutile [this message]
2015-02-19 17:20 ` Brian Foster
2015-02-19 17:25   ` Pratyush Anand
2015-02-19 21:37   ` Dave Chinner
2015-02-19 22:35     ` Don Dutile

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=54E66477.5060600@redhat.com \
    --to=ddutile@redhat.com \
    --cc=david@fromorbit.com \
    --cc=jbastian@redhat.com \
    --cc=panand@redhat.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    /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