mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Chao Yu <chao@kernel.org>, <jaegeuk@kernel.org>, <mhiramat@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] f2fs: fix the assign logic of iocb
Date: Thu, 20 Oct 2022 14:57:39 +0530	[thread overview]
Message-ID: <8cb1ce88-2e49-745a-dd40-29a084ce285b@quicinc.com> (raw)
In-Reply-To: <35c29f27-96c6-6d74-1efb-1588cbf430a2@kernel.org>

Hi,

On 10/20/2022 2:31 PM, Chao Yu wrote:
> On 2022/10/20 0:17, Mukesh Ojha wrote:
>> commit 18ae8d12991b ("f2fs: show more DIO information in tracepoint")
>> introduces iocb field in 'f2fs_direct_IO_enter' trace event
>> And it only assigns the pointer and later it accesses its field
>> in trace print log.
>>
>> Fix it by correcting data type and memcpy the content of iocb.
> 
> So the implementation below is wrong, right? since it just assign 
> __entry->name
> with dentry->d_name.name rather than copyiny entirely, so that, during 
> printing

I think, yes.

About the patch, we were getting error as below on doing

echo 51200 > /d/tracing/buffer_size_kb
echo 1 > /d/tracing/events/f2fs/f2fs_direct_IO_enter/enable
echo 1 > /d/tracing/tracing_on
cat /d/tracing/trace_pipe > ftrace.log

Run something which exercise this path.

Unable to handle kernel paging request at virtual address ffffffc04cef3d30
Mem abort info:
ESR = 0x96000007
EC = 0x25: DABT (current EL), IL = 32 bits

  pc : trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
  lr : trace_raw_output_f2fs_direct_IO_enter+0x2c/0xa4
  sp : ffffffc0443cbbd0
  x29: ffffffc0443cbbf0 x28: ffffff8935b120d0 x27: ffffff8935b12108
  x26: ffffff8935b120f0 x25: ffffff8935b12100 x24: ffffff8935b110c0
  x23: ffffff8935b10000 x22: ffffff88859a936c x21: ffffff88859a936c
  x20: ffffff8935b110c0 x19: ffffff8935b10000 x18: ffffffc03b195060
  x17: ffffff8935b11e76 x16: 00000000000000cc x15: ffffffef855c4f2c
  x14: 0000000000000001 x13: 000000000000004e x12: ffff0000ffffff00
  x11: ffffffef86c350d0 x10: 00000000000010c0 x9 : 000000000fe0002c
  x8 : ffffffc04cef3d28 x7 : 7f7f7f7f7f7f7f7f x6 : 0000000002000000
  x5 : ffffff8935b11e9a x4 : 0000000000006250 x3 : ffff0a00ffffff04
  x2 : 0000000000000002 x1 : ffffffef86a0a31f x0 : ffffff8935b10000
  Call trace:
   trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
   print_trace_fmt+0x9c/0x138
   print_trace_line+0x154/0x254
   tracing_read_pipe+0x21c/0x380
   vfs_read+0x108/0x3ac
   ksys_read+0x7c/0xec
   __arm64_sys_read+0x20/0x30
   invoke_syscall+0x60/0x150
   el0_svc_common.llvm.1237943816091755067+0xb8/0xf8
   do_el0_svc+0x28/0xa0

-Mukesh

  reply	other threads:[~2022-10-20  9:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 16:17 Mukesh Ojha
2022-10-20  9:01 ` Chao Yu
2022-10-20  9:27   ` Mukesh Ojha [this message]
2022-10-20 10:26     ` Chao Yu
2022-10-21  5:00 ` Pavan Kondeti
2022-10-24  5:07   ` Masami Hiramatsu

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=8cb1ce88-2e49-745a-dd40-29a084ce285b@quicinc.com \
    --to=quic_mojha@quicinc.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    /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

all inboxes | Powered by JetHome®