From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: mmotm 2019-04-19-14-53 uploaded (objtool)
Date: Fri, 19 Apr 2019 21:36:46 -0700 [thread overview]
Message-ID: <af3819b4-008f-171e-e721-a9a20f85d8d1@infradead.org> (raw)
In-Reply-To: <20190419215358.WMVFXV3bT%akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On 4/19/19 2:53 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2019-04-19-14-53 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
on x86_64:
CC lib/strncpy_from_user.o
lib/strncpy_from_user.o: warning: objtool: strncpy_from_user()+0x315: call to __ubsan_handle_add_overflow() with UACCESS enabled
CC lib/strnlen_user.o
lib/strnlen_user.o: warning: objtool: strnlen_user()+0x337: call to __ubsan_handle_sub_overflow() with UACCESS enabled
obj files are attached.
--
~Randy
[-- Attachment #2: strncpy_from_user.o --]
[-- Type: application/x-object, Size: 8480 bytes --]
[-- Attachment #3: strnlen_user.o --]
[-- Type: application/x-object, Size: 8064 bytes --]
next prev parent reply other threads:[~2019-04-20 4:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 21:53 mmotm 2019-04-19-14-53 uploaded akpm
2019-04-20 4:36 ` Randy Dunlap [this message]
2019-04-23 8:24 ` mmotm 2019-04-19-14-53 uploaded (objtool) Peter Zijlstra
2019-04-23 15:45 ` Randy Dunlap
2019-04-23 16:07 ` Andy Lutomirski
2019-04-23 17:39 ` Peter Zijlstra
2019-04-23 18:57 ` Peter Zijlstra
2019-04-23 16:19 ` Linus Torvalds
2019-04-23 17:35 ` Peter Zijlstra
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=af3819b4-008f-171e-e721-a9a20f85d8d1@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).