From: Paulo Alcantara <pc@manguebit.com>
To: Steve French <smfrench@gmail.com>
Cc: linux-cifs@vger.kernel.org
Subject: Re: [PATCH 4/9] smb: client: stop flooding dmesg in smb2_calc_signature()
Date: Wed, 25 Sep 2024 11:30:52 -0300 [thread overview]
Message-ID: <be8c5bf4a6241054e5e3c184c473f9bf@manguebit.com> (raw)
In-Reply-To: <CAH2r5mu5GNh1p4ns_B68AnsNN44o01A7LM6r21zK_j=ZfyyL0Q@mail.gmail.com>
Steve French <smfrench@gmail.com> writes:
> any thoughts on whether this should be at least a log once event? How
> to make it log at least once, but also something that could be turned
> on (doesn't seem like it makes sense to make it an dynamic trace point
> though ... right?)
Yep, having it logged once with "VFS | ONCE" would be fine. Feel free
to change it.
A dynamic trace point would be great, too. This could be done in a
separate patch.
next prev parent reply other threads:[~2024-09-25 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 5:15 [PATCH 1/9] smb: client: avoid unnecessary reconnects when refreshing referrals Paulo Alcantara
2024-09-18 5:15 ` [PATCH 2/9] smb: client: improve purging of cached referrals Paulo Alcantara
2024-09-18 5:15 ` [PATCH 3/9] smb: client: fix DFS interlink failover Paulo Alcantara
2024-09-18 5:15 ` [PATCH 4/9] smb: client: stop flooding dmesg in smb2_calc_signature() Paulo Alcantara
2024-09-25 2:23 ` Steve French
2024-09-25 14:30 ` Paulo Alcantara [this message]
2024-09-18 5:15 ` [PATCH 5/9] smb: client: print failed session logoffs with FYI Paulo Alcantara
2024-09-18 5:15 ` [PATCH 6/9] smb: client: stop flooding dmesg on failed session setups Paulo Alcantara
2024-09-18 5:15 ` [PATCH 7/9] smb: client: stop flooding dmesg with automounts Paulo Alcantara
2024-09-18 5:15 ` [PATCH 8/9] smb: client: fix DFS failover in multiuser mounts Paulo Alcantara
2024-09-18 5:15 ` [PATCH 9/9] smb: client: propagate error from cifs_construct_tcon() Paulo Alcantara
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=be8c5bf4a6241054e5e3c184c473f9bf@manguebit.com \
--to=pc@manguebit.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