From: David Howells <dhowells@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
netdev@vger.kernel.org, LKP <lkp@01.org>
Subject: Re: [lkp-robot] [bisect done] ace45bec6d [ 52.056290] EIP: lock_release
Date: Tue, 26 Jun 2018 14:25:00 +0100 [thread overview]
Message-ID: <32692.1530019500@warthog.procyon.org.uk> (raw)
In-Reply-To: <20180626010626.GG11011@yexl-desktop>
kernel test robot <lkp@intel.com> wrote:
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit ace45bec6d77bc061c3c3d8ad99e298ea9800c2b
> Author: David Howells <dhowells@redhat.com>
> AuthorDate: Fri Mar 30 21:04:43 2018 +0100
> Commit: David Howells <dhowells@redhat.com>
> CommitDate: Fri Mar 30 21:04:43 2018 +0100
>
> rxrpc: Fix firewall route keepalive
Are you actually making AF_RXRPC or the AFS filesystem do anything? Or is it
just happening spontaneously?
David
prev parent reply other threads:[~2018-06-26 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 1:06 [lkp-robot] [bisect done] ace45bec6d [ 52.056290] EIP: lock_release kernel test robot
2018-06-26 13:25 ` 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=32692.1530019500@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=lkp@01.org \
--cc=lkp@intel.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox