From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
jmorris@namei.org, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org, serge@hallyn.com
Subject: Re: kernel BUG at lib/assoc_array.c:LINE!
Date: Mon, 02 Mar 2020 09:27:21 +0000 [thread overview]
Message-ID: <686378.1583141241@warthog.procyon.org.uk> (raw)
In-Reply-To: <538780.1583137732@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> [ 621.627412][ T6728] kAFS: unable to lookup cell '?T]??J??n/P4?['
>
> This is a bit odd, since the version allegedly being tested includes a patch
> to prohibit AFS cell names that contain unprintable chars. It should error
> out in afs_alloc_cell(), way before it tries to do a DNS lookup.
Ah, no, that's okay. This error message is printed in afs_parse_source() on
the way out after afs_lookup_cell() fails (presumably due to afs_alloc_cell()
failing).
It seems unlikely that the dead process is actually anything to do with the
mount that more or less immediately preceded it in the log. It mount should
have failed without creating a cell record - which then precludes affecting
afs_manage_cell(). However, a previously created cell with a valid name can
feasibly be driving afs_manage_cell() and causing the problem.
David
prev parent reply other threads:[~2020-03-02 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 4:44 kernel BUG at lib/assoc_array.c:LINE! syzbot
2020-02-18 21:12 ` Jarkko Sakkinen
2020-03-02 8:28 ` David Howells
2020-03-02 9:27 ` David Howells [this message]
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=686378.1583141241@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).