From: Matthew Wilcox <willy@infradead.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Ira Weiny <ira.weiny@intel.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
Andrew Morton <akpm@linux-foundation.org>,
Bart Van Assche <bvanassche@acm.org>,
Kees Cook <keescook@chromium.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: kmap + memmove
Date: Mon, 6 May 2024 04:47:58 +0100 [thread overview]
Message-ID: <ZjhS7sE8chokLFrP@casper.infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2405051500030.3397@hadrien>
On Sun, May 05, 2024 at 03:01:56PM +0200, Julia Lawall wrote:
> On Sun, 5 May 2024, Matthew Wilcox wrote:
> > Here's a fun bug that's not obvious:
> >
> > hfs_bnode_move:
> > dst_ptr = kmap_local_page(*dst_page);
> > src_ptr = kmap_local_page(*src_page);
> > memmove(dst_ptr, src_ptr, src);
> >
> > If both of the pointers are guaranteed to come from diffeerent calls to
> > kmap_local(), memmove() is probably not going to do what you want.
> > Worth a smatch or coccinelle rule?
>
> I tried the following rule:
>
> @@
> expression dst_ptr, src_ptr, dst_page, src_page, src;
> @@
>
> * dst_ptr = kmap_local_page(dst_page);
> ... when any
> * src_ptr = kmap_local_page(src_page);
> ... when any
> * memmove(dst_ptr, src_ptr, src);
>
> That is, basically what you wrote, but with anything in between the lines,
> and the various variables being any expression.
>
> I only got the following results, which I guess are what you are already
> looking at:
Great, thanks! I tried something a little more crude:
$ git grep -A10 kmap_local |grep memmove
fs/erofs/decompressor.c- memmove(kin + rq->pageofs_out, kin + pi, cur);
fs/erofs/decompressor.c- memmove(kin + po,
fs/hfs/bnode.c- memmove(ptr + dst, ptr + src, len);
fs/hfsplus/bnode.c- memmove(dst_ptr, src_ptr, src);
fs/hfsplus/bnode.c- memmove(dst_ptr + src, src_ptr + src, len);
fs/hfsplus/bnode.c- memmove(dst_ptr, src_ptr, l);
fs/hfsplus/bnode.c- memmove(dst_ptr, src_ptr, l);
$ git grep -A10 kmap_atomic |grep memmove
net/sunrpc/xdr.c- memmove(vto + pgto_base, vto + pgfrom_base, copy);
net/sunrpc/xdr.c- memmove(vto + pgto_base, vto + pgfrom_base, copy);
All of these (other than hfsplus) are "false positives" in that you can
see the src/dst are from the same call to kmap_local/kmap_atomic. Glad
to see there's nothing else.
next prev parent reply other threads:[~2024-05-06 3:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 12:25 kmap + memmove Matthew Wilcox
2024-05-05 13:01 ` Julia Lawall
2024-05-06 3:40 ` Ira Weiny
2024-05-06 5:15 ` Julia Lawall
2024-05-06 5:48 ` Julia Lawall
2024-05-06 5:50 ` Julia Lawall
2024-05-06 3:47 ` Matthew Wilcox [this message]
2024-05-06 4:14 ` Matthew Wilcox
2024-05-24 19:35 ` Matthew Wilcox
2024-08-22 18:54 ` Matthew Wilcox
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=ZjhS7sE8chokLFrP@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=dan.carpenter@oracle.com \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=julia.lawall@inria.fr \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.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).