linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shyam Prasad N <nspmangalore@gmail.com>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: crediting/tracing related oops in xfstest 478
Date: Mon, 17 May 2021 16:50:02 +0530	[thread overview]
Message-ID: <CANT5p=oyGJuva3h-8ZzZRcNuDj5yd=M5emXDE1LpcNvXx+e+hA@mail.gmail.com> (raw)
In-Reply-To: <CANT5p=q8wbjhjgXsmu-OcnB4b5JndbZb-rHq+8e7kiK_gEVWLw@mail.gmail.com>

Correction, we should be having a ref to the server struct.
And it doesn't look like we free server->hostname, unless we have
dropped the ref to 0.

The call trace does seem a bit odd. I initially assumed that this came
from a regular file read.
However, I see some unexpected function names.
Is a procfs read somehow triggering this?

Needs more digging.

Regards,
Shyam

On Mon, May 17, 2021 at 2:51 PM Shyam Prasad N <nspmangalore@gmail.com> wrote:
>
> I'm guessing that this is because we neither hold the lock or get
> reference to server struct while we print these dynamic tracepoints.
> I fixed some of these by using local variables in my crediting
> patches. We should do it for others too.
> Let me spin a patch for this today.
>
> Regards,
> Shyam
>
> On Sat, May 15, 2021 at 10:03 PM Steve French <smfrench@gmail.com> wrote:
> >
> > Saw this oops running test 478 with tracing enabled
> >
> > .472990] run fstests generic/478 at 2021-05-15 11:27:59
> > [ 2308.033552] ------------[ cut here ]------------
> > [ 2308.033558] fmt: 'conn_id=0x%llx server=%s current_mid=%llu
> > credits=%d credit_change=%d in_flight=%d
> >                ' current_buffer: '   kworker/u24:6-243711  [004] ....
> > 2193.687129: smb3_add_credits: conn_id=0x1 server='
> > [ 2308.033570] WARNING: CPU: 0 PID: 244568 at
> > kernel/trace/trace.c:3759 trace_check_vprintf+0x3a5/0x3d0
> > [ 2308.033586] Modules linked in: cifs(OE) md4 nls_utf8 libdes rfcomm
> > nfnetlink cachefiles fscache netfs cmac algif_hash algif_skcipher
> > af_alg bnep nls_iso8859_1 intel_tcc_cooling x86_pkg_temp_thermal
> > intel_powerclamp coretemp snd_sof_pci_intel_cnl
> > snd_sof_intel_hda_common nouveau snd_soc_hdac_hda soundwire_intel
> > soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda
> > snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_hda_ext_core
> > snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mxm_wmi mei_hdcp
> > intel_rapl_msr drm_ttm_helper snd_ctl_led kvm_intel snd_soc_core
> > snd_hda_codec_realtek snd_compress iwlmvm snd_hda_codec_generic
> > snd_hda_codec_hdmi ttm ac97_bus kvm mac80211 uvcvideo
> > snd_pcm_dmaengine crct10dif_pclmul ghash_clmulni_intel drm_kms_helper
> > snd_hda_intel videobuf2_vmalloc videobuf2_memops btusb aesni_intel
> > btrtl crypto_simd btbcm videobuf2_v4l2 cec cryptd snd_seq_midi libarc4
> > snd_intel_dspcfg btintel snd_intel_sdw_acpi videobuf2_common
> > snd_seq_midi_event snd_hda_codec rapl rc_core
> > [ 2308.033718]  videodev fb_sys_fops intel_cstate snd_rawmidi
> > snd_hda_core iwlwifi bluetooth syscopyarea thinkpad_acpi snd_hwdep
> > mei_me sysfillrect input_leds sysimgblt processor_thermal_device nvram
> > snd_seq processor_thermal_rfim serio_raw snd_pcm joydev
> > platform_profile efi_pstore mc nvidiafb ucsi_acpi
> > processor_thermal_mbox vgastate processor_thermal_rapl ecdh_generic
> > wmi_bmof elan_i2c intel_wmi_thunderbolt mei cfg80211 fb_ddc typec_ucsi
> > ee1004 intel_rapl_common snd_seq_device ecc 8250_dw ledtrig_audio
> > i2c_algo_bit intel_pch_thermal intel_soc_dts_iosf typec snd_timer snd
> > soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid
> > acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport
> > drm sunrpc ip_tables x_tables autofs4 xfs btrfs blake2b_generic xor
> > zstd_compress raid6_pq libcrc32c wacom hid_generic usbhid hid
> > rtsx_pci_sdmmc crc32_pclmul psmouse nvme e1000e i2c_i801 nvme_core
> > i2c_smbus rtsx_pci intel_lpss_pci intel_lpss xhci_pci idma64
> > xhci_pci_renesas wmi
> > [ 2308.033867]  video pinctrl_cannonlake [last unloaded: cifs]
> > [ 2308.033876] CPU: 0 PID: 244568 Comm: trace-cmd Tainted: G
> > OE     5.13.0-051300rc1-generic #202105092230
> > [ 2308.033884] Hardware name: LENOVO 20MAS08500/20MAS08500, BIOS
> > N2CET54W (1.37 ) 06/20/2020
> > [ 2308.033887] RIP: 0010:trace_check_vprintf+0x3a5/0x3d0
> > [ 2308.033897] Code: 00 00 48 39 c8 72 2e 39 c8 74 2a c6 04 0a 00 49
> > 8b 97 b0 20 00 00 48 8b 75 b0 48 c7 c7 e8 29 bd 95 44 89 55 d0 e8 85
> > 8e a1 00 <0f> 0b 44 8b 55 d0 e9 13 ff ff ff c6 44 02 ff 00 49 8b 97 b0
> > 20 00
> > [ 2308.033903] RSP: 0018:ffffb52c864fbc40 EFLAGS: 00010286
> > [ 2308.033910] RAX: 0000000000000000 RBX: 0000000000000017 RCX: ffffa017bba189c8
> > [ 2308.033915] RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffffa017bba189c0
> > [ 2308.033919] RBP: ffffb52c864fbc90 R08: 0000000000000000 R09: ffffb52c864fba38
> > [ 2308.033922] R10: ffffb52c864fba30 R11: ffffffff96555148 R12: ffffffffc170eb3e
> > [ 2308.033926] R13: ffffa010c4f2fdf0 R14: ffffffffc170eb28 R15: ffffa010d8bcc000
> > [ 2308.033930] FS:  00007f6c8ad38740(0000) GS:ffffa017bba00000(0000)
> > knlGS:0000000000000000
> > [ 2308.033936] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 2308.033940] CR2: 000055ab9413e9c8 CR3: 0000000104aee006 CR4: 00000000003706f0
> > [ 2308.033946] Call Trace:
> > [ 2308.033956]  trace_event_printf+0x5e/0x80
> > [ 2308.033967]  trace_raw_output_smb3_credit_class+0x56/0x70 [cifs]
> > [ 2308.034071]  print_trace_fmt+0x10f/0x1c0
> > [ 2308.034081]  print_trace_line+0xc7/0x140
> > [ 2308.034087]  s_show+0x4c/0x160
> > [ 2308.034094]  seq_read_iter+0x2fb/0x520
> > [ 2308.034105]  seq_read+0xfa/0x140
> > [ 2308.034116]  vfs_read+0xa0/0x190
> > [ 2308.034122]  ksys_read+0x67/0xe0
> > [ 2308.034129]  __x64_sys_read+0x1a/0x20
> > [ 2308.034135]  do_syscall_64+0x40/0xb0
> > [ 2308.034143]  entry_SYSCALL_64_after_hwframe+0x44/0xae
> > [ 2308.034153] RIP: 0033:0x7f6c8ae42b82
> > [ 2308.034159] Code: c0 e9 b2 fe ff ff 50 48 8d 3d ba aa 0a 00 e8 65
> > 08 02 00 0f 1f 44 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75
> > 10 0f 05 <48> 3d 00 f0 ff ff 77 56 c3 0f 1f 44 00 00 48 83 ec 28 48 89
> > 54 24
> > [ 2308.034165] RSP: 002b:00007fff0909aa18 EFLAGS: 00000246 ORIG_RAX:
> > 0000000000000000
> > [ 2308.034172] RAX: ffffffffffffffda RBX: 000055ab9413d330 RCX: 00007f6c8ae42b82
> > [ 2308.034176] RDX: 0000000000002000 RSI: 00007fff0909aab0 RDI: 0000000000000003
> > [ 2308.034180] RBP: 00007f6c8af1d4a0 R08: 0000000000000003 R09: 000055ab9413d9c0
> > [ 2308.034183] R10: 0000000000000077 R11: 0000000000000246 R12: 0000000000002000
> > [ 2308.034187] R13: 00007fff0909aab0 R14: 0000000000000d68 R15: 00007f6c8af1c8a0
> > [ 2308.034194] ---[ end trace c27dbcf0cab73015 ]---
> >
> >
> > --
> > Thanks,
> >
> > Steve
>
>
>
> --
> Regards,
> Shyam



-- 
Regards,
Shyam

      reply	other threads:[~2021-05-17 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 16:33 crediting/tracing related oops in xfstest 478 Steve French
2021-05-17  9:21 ` Shyam Prasad N
2021-05-17 11:20   ` Shyam Prasad N [this message]

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='CANT5p=oyGJuva3h-8ZzZRcNuDj5yd=M5emXDE1LpcNvXx+e+hA@mail.gmail.com' \
    --to=nspmangalore@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.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;
as well as URLs for NNTP newsgroup(s).