From: David Howells <dhowells@redhat.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: dhowells@redhat.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 08:28:52 +0000 [thread overview]
Message-ID: <538780.1583137732@warthog.procyon.org.uk> (raw)
In-Reply-To: <20200218211259.GA19673@linux.intel.com>
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
> The arguments for request_key_and_link() are fairly constrained:
>
> type == &key_type_dns_resolver
> description == "afsdb:<cell name>"
> domain_tag == net->key_domain
> callout_info == "srv=1"
> callout_len == 5
> aux == NULL
> dest_keyring == NULL
> flags == KEY_ALLOC_IN_QUOTA
>
> (manually resolved)
>
> The only obvious moving part I see is the key type implementatio i.e.
> net/dns_resolver/dns_key.c.
It shouldn't matter what the payload of the key is going to be, but it might
matter what the cell name is. Looking in the log, I see this:
mount(&(0x7f0000000000)=ANY=[@ANYBLOB="25dc545df1e34ab2e26e2f5034c85b3a"], &(0x7f0000000140)='./file0\x00', &(0x7f0000000180)='afs\x00', 0x0, 0x0)
The:
@ANYBLOB="25dc545df1e34ab2e26e2f5034c85b3a"
is the source, i.e.:
%\xdcT]\xf1\xe3J\xb2\xe2n/P4\xc8[':
This is in the form "[%#][<cellname>:]<volumename>", which comports with the
log:
[ 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.
David
next prev parent reply other threads:[~2020-03-02 8:29 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 [this message]
2020-03-02 9:27 ` David Howells
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=538780.1583137732@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).