From: Alex McWhirter <alexmcwhirter@triadic.us>
To: sparclinux@vger.kernel.org
Subject: Re: Kernels 4.+ are breaking rsync?
Date: Thu, 03 Mar 2016 06:31:53 +0000 [thread overview]
Message-ID: <56D7DA59.1050201@triadic.us> (raw)
In-Reply-To: <56C11585.3060503@triadic.us>
On 02/28/2016 12:57 PM, Al Viro wrote:
> On Sun, Feb 28, 2016 at 06:41:37PM +0100, Sam Ravnborg wrote:
>> On Sun, Feb 21, 2016 at 09:14:45PM +0100, Sam Ravnborg wrote:
>>> Added Al Viro, as author of the commit git bisect pointed out.
>> Al, have you by chance looked at this bug report?
> Not enough details...
>
>> Alex, did you try to revert just this single patch on mainline
>> to verify this _is_ indeed the culprint?
> Not a chance - a lot of stuff past it depends on that series.
>
> How does rsync die there? oops, segfault, something else? Any way to
> reproduce it?
Also you should be able to reproduce it on any sun4u hardware, as it
occurs on all of my boxes. Sun4v may paint a different picture.
next prev parent reply other threads:[~2016-03-03 6:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 0:02 Kernels 4.+ are breaking rsync? Alex McWhirter
2016-02-21 18:52 ` Alex McWhirter
2016-02-21 20:13 ` Sam Ravnborg
2016-02-21 20:14 ` Sam Ravnborg
2016-02-28 17:41 ` Sam Ravnborg
2016-02-28 17:57 ` Al Viro
2016-03-03 6:29 ` Alex McWhirter
2016-03-03 6:31 ` Alex McWhirter [this message]
2016-03-03 6:50 ` John Paul Adrian Glaubitz
2016-03-03 6:50 ` Alex McWhirter
2016-03-03 6:57 ` John Paul Adrian Glaubitz
2016-03-03 7:03 ` Alex McWhirter
2016-03-03 7:43 ` John Paul Adrian Glaubitz
2016-03-04 20:47 ` John Paul Adrian Glaubitz
2016-03-04 21:41 ` John Paul Adrian Glaubitz
2016-03-08 3:28 ` Alex McWhirter
-- strict thread matches above, loose matches on Subject: below --
2016-03-04 20:24 alexmcwhirter
2016-03-04 21:21 ` alexmcwhirter
2016-03-09 22:10 ` alexmcwhirter
2016-03-16 17:10 ` alexmcwhirter
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=56D7DA59.1050201@triadic.us \
--to=alexmcwhirter@triadic.us \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.