From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: Kernels 4.+ are breaking rsync?
Date: Sun, 21 Feb 2016 20:13:24 +0000 [thread overview]
Message-ID: <20160221201324.GA24601@ravnborg.org> (raw)
In-Reply-To: <56C11585.3060503@triadic.us>
On Sun, Feb 21, 2016 at 01:52:55PM -0500, Alex McWhirter wrote:
> On 02/14/2016 07:02 PM, Alex McWhirter wrote:
> > I having a strange issue where using any 4.X kernel causes rsync to
> > appear to die on a select syscall. Not sure why, maybe it's getting a
> > wrong file descriptor or something. Unfortunately this starts pushing
> > outside of my knowledge level of linux so bear with me. This is on a Sun
> > V215 but i have also tested it on a Sun Blade 150 and a Sun Ultra 45
> > with the same results. These are all sun4u boxes of course, i haven't
> > tried any sun4v boxes. I''l try to spin up a T5120 this week and find
> > out if it's also an issue on sun4v.
> >
> > Here's what I've tested.
> >
> > 3.14.58 "gentoo" - Works
> > 3.18.26 "vanilla" - Works
> > 4.1.15 "gentoo" - Dead
> > 4.1.17 "vanilla" - Dead
> > 4.4.1 "vanilla" - Dead
> >
> > I don't mind hacking away at kernel sources if anyone can point me in
> > the right direction. It's also worth noting that this only happens when
> > the folder i am attempting to rsync is significantly large in regards to
> > the amount of sub-folders and files. The Gentoo portage tree in particular.
> >
> > Attached is the strace output of a failing rsync job.
> >
> >
>
> I've traced this down a bit further.
>
> Kernel 3.18.26 is working but 3.19.0 is not. Git bisect traced it down
> to this commit.
>
> e5a4b0bb803b39a36478451eae53a880d2663d5b is the first bad commit
> commit e5a4b0bb803b39a36478451eae53a880d2663d5b
Well done!
Did you try to revert the offending commit on top of a faulty
kernel, just to double check this is the guilty commit?
Sam
next prev parent reply other threads:[~2016-02-21 20:13 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 [this message]
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
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=20160221201324.GA24601@ravnborg.org \
--to=sam@ravnborg.org \
--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.