From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
ajd@linux.ibm.com, aneesh.kumar@linux.ibm.com,
atrajeev@linux.vnet.ibm.com, christophe.leroy@csgroup.eu,
cuigaosheng1@huawei.com, david@redhat.com, farosas@linux.ibm.com,
geoff@infradead.org, gustavoars@kernel.org, haren@linux.ibm.com,
hbathini@linux.ibm.com, joel@jms.id.au, lihuafei1@huawei.com,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
linuxppc-dev@lists.ozlabs.org, lukas.bulwahn@gmail.com,
mikey@neuling.org, nathan@kernel.org, nathanl@linux.ibm.com,
nicholas@linux.ibm.com, npiggin@gmail.com, pali@kernel.org,
paul@paul-moore.com, rmclure@linux.ibm.com, ruscur@russell.cc,
windhl@126.com, wsa+renesas@sang-engineering.com,
ye.xingchen@zte.com.cn, yuanjilin@cdjrlc.com,
zhengyongjun3@huawei.com
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-6.1-1 tag
Date: Mon, 10 Oct 2022 20:57:54 -0600 [thread overview]
Message-ID: <Y0Tbsh7Zeodxueux@zx2c4.com> (raw)
In-Reply-To: <874jwbnn1u.fsf@mpe.ellerman.id.au>
On Tue, Oct 11, 2022 at 12:53:17PM +1100, Michael Ellerman wrote:
> "Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> > On Mon, Oct 10, 2022 at 01:25:25PM -0600, Jason A. Donenfeld wrote:
> >> Hi Michael,
> >>
> >> On Sun, Oct 09, 2022 at 10:01:39PM +1100, Michael Ellerman wrote:
> >> > powerpc updates for 6.1
> >> >
> >> > - Remove our now never-true definitions for pgd_huge() and p4d_leaf().
> >> >
> >> > - Add pte_needs_flush() and huge_pmd_needs_flush() for 64-bit.
> >> >
> >> > - Add support for syscall wrappers.
> >> >
> >> > - Add support for KFENCE on 64-bit.
> >> >
> >> > - Update 64-bit HV KVM to use the new guest state entry/exit accounting API.
> >> >
> >> > - Support execute-only memory when using the Radix MMU (P9 or later).
> >> >
> >> > - Implement CONFIG_PARAVIRT_TIME_ACCOUNTING for pseries guests.
> >> >
> >> > - Updates to our linker script to move more data into read-only sections.
> >> >
> >> > - Allow the VDSO to be randomised on 32-bit.
> >> >
> >> > - Many other small features and fixes.
> >>
> >> FYI, something in here broke the wireguard test suite, which runs the
> >> iperf3 networking utility. The full log is here [1], but the relevant part
> >> is:
> >>
> >> [+] NS1: iperf3 -Z -t 3 -c 192.168.241.2
> >> Connecting to host 192.168.241.2, port 5201
> >> iperf3: error - failed to read /dev/urandom: Bad address
> >>
> >> I'll see if I can narrow it down a bit more and bisect. But just FYI, in
> >> case you have an intuition.
> >
> > Huh. From iov_iter.c:
> >
> > static int copyout(void __user *to, const void *from, size_t n)
> > {
> > size_t before = n;
> > if (should_fail_usercopy())
> > return n;
> > if (access_ok(to, n)) {
> > instrument_copy_to_user(to, from, n);
> > n = raw_copy_to_user(to, from, n);
> > if (n == before)
> > pr_err("SARU n still %zu pointer is %lx\n", n, (unsigned long)to);
> > }
> > return n;
> > }
> >
> > I added the pr_err() there to catch the failure:
> > [ 3.443506] SARU n still 64 pointer is b78db000
> >
> > Also I managed to extract the failing portion of iperf3 into something
> > smaller:
> >
> > int temp;
> > char *x;
> > ssize_t l;
> > FILE *f;
> > char template[] = "/blah-XXXXXX";
> >
> > temp = mkstemp(template);
> > if (temp < 0)
> > panic("mkstemp");
> > if (unlink(template) < 0)
> > panic("unlink");
> > if (ftruncate(temp, 0x20000) < 0)
> > panic("ftruncate");
> > x = mmap(NULL, 0x20000, PROT_READ|PROT_WRITE, MAP_PRIVATE, temp, 0);
> > if (x == MAP_FAILED)
> > panic("mmap");
> > f = fopen("/dev/urandom", "rb");
> > if (!f)
> > panic("fopen");
> > setbuf(f, NULL);
> > if (fread(x, 1, 0x20000, f) != 0x20000)
> > panic("fread");
>
> Does that fail for you reliably?
>
> It succeeds for me running under qemu ppce500, though I'm not using your
> kernel config yet.
Yes, every time without fail, across two systems and two qemu builds.
Jason
next prev parent reply other threads:[~2022-10-11 2:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 11:01 [GIT PULL] Please pull powerpc/linux.git powerpc-6.1-1 tag Michael Ellerman
2022-10-09 21:17 ` pr-tracker-bot
2022-10-10 19:25 ` Jason A. Donenfeld
2022-10-10 20:03 ` Jason A. Donenfeld
2022-10-10 22:26 ` Jason A. Donenfeld
2022-10-11 0:00 ` Andrew Donnellan
2022-10-11 0:13 ` Jason A. Donenfeld
2022-10-11 1:44 ` Michael Ellerman
2022-10-11 2:57 ` Jason A. Donenfeld
2022-10-11 9:34 ` Michael Ellerman
2022-10-11 1:53 ` Michael Ellerman
2022-10-11 2:57 ` Jason A. Donenfeld [this message]
2022-10-11 9:35 ` Michael Ellerman
2022-10-11 11:10 ` Nicholas Piggin
2022-10-12 14:18 ` Guenter Roeck
2022-10-12 15:49 ` Jason A. Donenfeld
2022-10-12 16:44 ` Guenter Roeck
2022-10-12 17:20 ` Jason A. Donenfeld
2022-10-12 17:48 ` Guenter Roeck
2022-10-12 18:37 ` Jason A. Donenfeld
2022-10-13 5:17 ` Nicholas Piggin
2022-10-12 22:16 ` Guenter Roeck
2022-10-13 0:03 ` Michael Ellerman
2022-10-13 0:21 ` Guenter Roeck
2022-10-13 5:03 ` Nicholas Piggin
2022-10-13 5:19 ` Jason A. Donenfeld
2022-10-13 5:20 ` Guenter Roeck
2022-10-13 5:22 ` Nicholas Piggin
2022-10-13 4:43 ` Guenter Roeck
2022-10-13 5:14 ` Nicholas Piggin
2022-10-13 18:55 ` Guenter Roeck
2022-10-12 16:45 ` Jason A. Donenfeld
2022-10-12 16:49 ` Guenter Roeck
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=Y0Tbsh7Zeodxueux@zx2c4.com \
--to=jason@zx2c4.com \
--cc=ajd@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=cuigaosheng1@huawei.com \
--cc=david@redhat.com \
--cc=farosas@linux.ibm.com \
--cc=geoff@infradead.org \
--cc=gustavoars@kernel.org \
--cc=haren@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=nathanl@linux.ibm.com \
--cc=nicholas@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pali@kernel.org \
--cc=paul@paul-moore.com \
--cc=rmclure@linux.ibm.com \
--cc=ruscur@russell.cc \
--cc=torvalds@linux-foundation.org \
--cc=windhl@126.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=ye.xingchen@zte.com.cn \
--cc=yuanjilin@cdjrlc.com \
--cc=zhengyongjun3@huawei.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