From: Mike Kazantsev <mk.fraggod@gmail.com>
To: ntfs3@lists.linux.dev
Subject: memcpy: detected field-spanning write (size 8) of single field "le->name"
Date: Mon, 25 Sep 2023 17:59:25 +0500 [thread overview]
Message-ID: <20230925175925.20fca707@malediction> (raw)
Hi,
Running latest stable linux kernels, I seem to have this WARNING pop-up
under specific "create/write multiple 1-2M files per second" workload
on ntfs3 mountpoint (generated by aria2c downloader for youtube DASH
videos via yt-dlp):
memcpy: detected field-spanning write (size 8) of single field
"le->name" at fs/ntfs3/attrlist.c:326 (size 6)
I think this is a warning from security/sanity checks introduced in 6.x
at some point, and might not be an actual problem that breaks anything.
But presumably warnings still shouldn't be emitted, and fix might to
split the write in two, if it's intentionally overwriting the next
field as well, or mark it in the code as a non-issue somehow.
I've initially reported it at https://bugzilla.kernel.org/show_bug.cgi?id=217937
but it was suggested there to post it to this mailing list instead.
See couple backtraces (which seem to be rather easily reproducible) attached there.
Didn't look into the issue myself, but thought to report it anyway,
in case it might be useful, and maybe trivial to fix.
Cheers!
--
Mike Kazantsev // fraggod.net
reply other threads:[~2023-09-25 12:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230925175925.20fca707@malediction \
--to=mk.fraggod@gmail.com \
--cc=ntfs3@lists.linux.dev \
/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