From: David Howells <dhowells@redhat.com>
To: Oliver Sang <oliver.sang@intel.com>
Cc: dhowells@redhat.com, oe-lkp@lists.linux.dev, lkp@intel.com,
Steve French <sfrench@samba.org>,
Shyam Prasad N <nspmangalore@gmail.com>,
"Rohith Surabattula" <rohiths.msft@gmail.com>,
Jeff Layton <jlayton@kernel.org>,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org
Subject: Re: [dhowells-fs:cifs-netfs] [cifs] b4834f12a4: WARNING:at_fs/netfs/write_collect.c:#netfs_writeback_lookup_folio
Date: Fri, 26 Apr 2024 09:34:02 +0100 [thread overview]
Message-ID: <2145544.1714120442@warthog.procyon.org.uk> (raw)
In-Reply-To: <Zin4G2VYUiaYxsKQ@xsang-OptiPlex-9020>
Oliver Sang <oliver.sang@intel.com> wrote:
> I can pass "sudo bin/lkp install job.yaml" on my local machine with fedora 39
> now.
Note that this causes:
systemd-sysv-generator[23561]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. ♻️ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ⚠️ This compatibility logic is deprecated, expect removal soon. ⚠️
to appear. What's it doing to the networking settings? It shouldn't be
touching those.
Also, does it have to install its own cifs server? Can it not be directed to
my test server that's already set up on another machine? And does it have to
build a kernel? Can it not use the one that's already running on the machine?
David
next prev parent reply other threads:[~2024-04-26 8:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 4:42 [dhowells-fs:cifs-netfs] [cifs] b4834f12a4: WARNING:at_fs/netfs/write_collect.c:#netfs_writeback_lookup_folio kernel test robot
2024-04-17 12:18 ` David Howells
2024-04-25 6:28 ` Oliver Sang
2024-04-26 8:34 ` David Howells [this message]
2024-05-14 8:20 ` Oliver Sang
2024-04-26 8:52 ` David Howells
2024-04-26 8:56 ` David Howells
2024-05-14 8:24 ` Oliver Sang
2024-05-14 8:23 ` Oliver Sang
2024-04-26 9:04 ` David Howells
2024-05-14 8:25 ` Oliver Sang
2024-04-26 9:42 ` David Howells
2024-04-26 10:59 ` Philip Li
2024-05-14 8:45 ` Oliver Sang
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=2145544.1714120442@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netfs@lists.linux.dev \
--cc=nspmangalore@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=rohiths.msft@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.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