From: Oliver Sang <oliver.sang@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Christian Brauner <brauner@kernel.org>,
Jeff Layton <jlayton@kernel.org>, <netfs@lists.linux.dev>,
<linux-fsdevel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [linux-next:master] [netfs] a05b682d49: BUG:KASAN:slab-use-after-free_in_copy_from_iter
Date: Thu, 19 Sep 2024 10:50:03 +0800 [thread overview]
Message-ID: <ZuuRW82LGwgiVz/n@xsang-OptiPlex-9020> (raw)
In-Reply-To: <2377098.1726668218@warthog.procyon.org.uk>
hi, David,
sorry that we only have initial support for fedora
https://github.com/intel/lkp-tests?tab=readme-ov-file#supported-distributions
we will look this issue. however, due to resource constraint, we may not be
able to supply quick support.
btw, for this case, it really need 4 hdd partitions, so need refer to
https://github.com/intel/lkp-tests?tab=readme-ov-file#run-your-own-disk-partitions
On Wed, Sep 18, 2024 at 03:03:38PM +0100, David Howells wrote:
> Hi Oliver,
>
> The reproducer script doesn't manage to build (I'm using Fedora 39):
>
> + /usr/lib/rpm/check-rpaths
> *******************************************************************************
> *
> * WARNING: 'check-rpaths' detected a broken RPATH OR RUNPATH and will cause
> * 'rpmbuild' to fail. To ignore these errors, you can set the
> * '$QA_RPATHS' environment variable which is a bitmask allowing the
> * values below. The current value of QA_RPATHS is 0x0000.
> *
> * 0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
> * issue but are introducing redundant searchpaths without
> * providing a benefit. They can also cause errors in multilib
> * environments.
> * 0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
> * nor relative filenames and can therefore be a SECURITY risk
> * 0x0004 ... insecure RPATHs; these are relative RPATHs which are a
> * SECURITY risk
> * 0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
> * RPATHs; this is just a minor issue but usually unwanted
> * 0x0010 ... the RPATH is empty; there is no reason for such RPATHs
> * and they cause unneeded work while loading libraries
> * 0x0020 ... an RPATH references '..' of an absolute path; this will break
> * the functionality when the path before '..' is a symlink
> *
> *
> * Examples:
> * - to ignore standard and empty RPATHs, execute 'rpmbuild' like
> * $ QA_RPATHS=$(( 0x0001|0x0010 )) rpmbuild my-package.src.rpm
> * - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
> * $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
> *
> *******************************************************************************
> ERROR 0002: file '/usr/local/sbin/fsck.f2fs' contains an invalid runpath '/usr/local/lib' in [/usr/local/lib]
> ERROR 0002: file '/usr/local/sbin/mkfs.f2fs' contains an invalid runpath '/usr/local/lib' in [/usr/local/lib]
> ERROR 0002: file '/usr/local/lib/libf2fs_format.so.9.0.0' contains an invalid runpath '/usr/local/lib' in [/usr/local/lib]
> error: Bad exit status from /var/tmp/rpm-tmp.ASUBws (%install)
>
> RPM build warnings:
> source_date_epoch_from_changelog set but %changelog is missing
>
> RPM build errors:
> Bad exit status from /var/tmp/rpm-tmp.ASUBws (%install)
> error: open of /mnt2/lkp-tests/programs/xfstests/pkg/rpm_build/RPMS/xfstests-LKP.rpm failed: No such file or directory
> ==> WARNING: Failed to install built package(s).
>
next prev parent reply other threads:[~2024-09-19 2:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 7:24 kernel test robot
2024-09-13 7:59 ` David Howells
2024-09-13 8:11 ` Christian Brauner
2024-09-18 2:24 ` Oliver Sang
2024-09-18 10:34 ` David Howells
2024-09-18 11:27 ` David Howells
2024-09-19 2:23 ` Oliver Sang
2024-09-19 7:14 ` David Howells
2024-09-20 6:36 ` Oliver Sang
2024-09-20 7:55 ` David Howells
2024-09-18 14:03 ` David Howells
2024-09-19 2:50 ` Oliver Sang [this message]
2024-09-24 21:47 ` David Howells
2024-09-24 23:19 ` Steve French
2024-09-26 2:20 ` 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=ZuuRW82LGwgiVz/n@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=netfs@lists.linux.dev \
--cc=oe-lkp@lists.linux.dev \
/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