From: Al Viro <viro@ZenIV.linux.org.uk>
To: Matthew McClintock <mmcclint@codeaurora.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression in 4.6.0-git - bisected to commit dd254f5a382c
Date: Wed, 25 May 2016 04:21:49 +0100 [thread overview]
Message-ID: <20160525032148.GD14480@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20D5CE99-E85C-4D4A-97C0-7BD743FF92CD@codeaurora.org>
On Tue, May 24, 2016 at 09:06:03PM -0500, Matthew McClintock wrote:
>
> > On May 24, 2016, at 8:28 PM, Al Viro <viro@ZenIV.linux.org.uk> wrote:
> >
> > The next obvious question is which binary it is and what's the return
> > address to userland; make that
> > if (!size)
> > printk(KERN_ERR "crap in %s[%x]",
> > current->comm,
> > current_pt_regs()->rip);
> > (in the same place)
>
> This is an ARM board, no rip. Quick log without, can re-run again later tonight or maybe tomorrow:
probably ->ARM_pc, then...
> [ 8.008054] crap in udevd
Indeed. Which version of that Fine Piece Of Software is it? Again, the
kernel-side bug is real and needs fixing, but "udev does something bogus"
is not surprising in the slightest...
next prev parent reply other threads:[~2016-05-25 3:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 21:30 Regression in 4.6.0-git - bisected to commit dd254f5a382c Larry Finger
2016-05-24 0:18 ` Al Viro
2016-05-24 2:55 ` Larry Finger
2016-05-24 16:10 ` Larry Finger
2016-05-24 16:28 ` Al Viro
2016-05-24 18:39 ` Larry Finger
2016-05-24 19:13 ` Matthew McClintock
2016-05-24 19:16 ` Larry Finger
2016-05-24 19:25 ` Matthew McClintock
2016-05-24 19:36 ` Larry Finger
2016-05-24 22:31 ` Matthew McClintock
2016-05-24 23:41 ` Al Viro
2016-05-25 0:58 ` Matthew McClintock
2016-05-25 1:10 ` Al Viro
2016-05-25 1:20 ` Matthew McClintock
2016-05-25 1:28 ` Al Viro
2016-05-25 2:06 ` Matthew McClintock
2016-05-25 3:21 ` Al Viro [this message]
2016-05-25 6:24 ` Al Viro
2016-05-25 14:28 ` Larry Finger
2016-05-25 15:27 ` Matthew McClintock
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=20160525032148.GD14480@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mmcclint@codeaurora.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.