Hi Linus,
On Tue, Oct 17, 2023 at 10:43 AM Linus Torvalds
wrote:
>
> On Tue, 17 Oct 2023 at 10:04, Linus Torvalds
> wrote:
> >
> > Honestly, there is only two kinds of sealing that makes sense:
> >
> > - you cannot change the permissions of some area
> >
> > - you cannot unmap an area
>
> Actu
rnel.org/r/20231016203548.21993-1-marpagan%40redhat.com
patch subject: [PATCH] kunit: run test suites only after module initialization
completes
config: csky-randconfig-002-20231018
(https://download.01.org/0day-ci/archive/20231018/202310181220.us7bvp16-...@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
Commit 20d96b25cc4c ("selftests/resctrl: Fix schemata write error
check") exposed a problem in feature detection logic in MBM selftest.
If schemata does not support MB:x=x entries, the schemata write to
initialize 100% memory bandwidth allocation in mbm_setup() will now
fail with -EINVAL due to the
On Wed, 18 Oct 2023, Ilpo Järvinen wrote:
> Commit 20d96b25cc4c ("selftests/resctrl: Fix schemata write error
> check") exposed a problem in feature detection logic in MBM selftest.
> If schemata does not support MB:x=x entries, the schemata write to
> initialize 100% memory bandwidth allocation i
Hello,
On Fri, Oct 13, 2023 at 02:11:19PM -0400, Waiman Long wrote:
> When the "isolcpus" boot command line option is used to add a set
> of isolated CPUs, those CPUs will be excluded automatically from
> wq_unbound_cpumask to avoid running work functions from unbound
> workqueues.
>
> Recently c
On Fri, Oct 13, 2023 at 02:11:21PM -0400, Waiman Long wrote:
...
> @@ -3875,6 +3931,13 @@ static struct cftype dfl_files[] = {
> .flags = CFTYPE_ONLY_ON_ROOT | CFTYPE_DEBUG,
> },
>
> + {
> + .name = "cpus.isolated",
> + .seq_show = cpuset_common_seq
On 10/18/23 05:26, Tejun Heo wrote:
On Fri, Oct 13, 2023 at 02:11:21PM -0400, Waiman Long wrote:
...
@@ -3875,6 +3931,13 @@ static struct cftype dfl_files[] = {
.flags = CFTYPE_ONLY_ON_ROOT | CFTYPE_DEBUG,
},
+ {
+ .name = "cpus.isolated",
+
On 10/18/23 05:24, Tejun Heo wrote:
Hello,
On Fri, Oct 13, 2023 at 02:11:19PM -0400, Waiman Long wrote:
When the "isolcpus" boot command line option is used to add a set
of isolated CPUs, those CPUs will be excluded automatically from
wq_unbound_cpumask to avoid running work functions from unbo
If name_show() is non unique, this test will try to install a kprobe on this
function which should fail returning EADDRNOTAVAIL.
On kernel where name_show() is not unique, this test is skipped.
Signed-off-by: Francis Laniel
---
.../ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc | 13 +++
On Tue, Oct 17, 2023 at 9:54 AM Linus Torvalds
wrote:
>
> On Tue, 17 Oct 2023 at 02:08, wrote:
> >
> > Of all the call paths that call into do_vmi_munmap(),
> > this is the only place where checkSeals = MM_SEAL_MUNMAP.
> > The rest has checkSeals = 0.
>
> Why?
>
> None of this makes sense.
>
> So
On Tue, Oct 17, 2023 at 08:18:47PM -0700, Jeff Xu wrote:
> In practice: libc could do below:
> #define MM_IMMUTABLE
> (MM_SEAL_MPROTECT|MM_SEAL_MUNMAP|MM_SEAL_MREMAP|MM_SEAL_MMAP)
> mseal(add,len, MM_IMMUTABLE)
> it will be equivalent to BSD's immutable().
No, it wouldn't, because you've carefully
On Mon, Oct 16, 2023 at 11:17:56AM -0700, Nicolin Chen wrote:
> On Mon, Oct 16, 2023 at 08:54:07AM -0300, Jason Gunthorpe wrote:
> > On Mon, Oct 16, 2023 at 11:28:15AM +0800, Yi Liu wrote:
> > > On 2023/10/14 01:56, Nicolin Chen wrote:
> > > > On Fri, Oct 13, 2023 at 11:04:56AM -0300, Jason Gunthor
On Tue, Oct 17, 2023 at 12:58:39PM -0700, Nicolin Chen wrote:
> On Tue, Oct 17, 2023 at 12:53:01PM -0300, Jason Gunthorpe wrote:
> > On Tue, Oct 17, 2023 at 08:52:49AM +, Tian, Kevin wrote:
> > > I prefer to removing enforce_cc in attach fn completely then no parent
> > > trick in this patch. J
On Wed, Oct 18, 2023 at 01:37:20PM -0300, Jason Gunthorpe wrote:
> On Mon, Oct 16, 2023 at 11:17:56AM -0700, Nicolin Chen wrote:
> > On Mon, Oct 16, 2023 at 08:54:07AM -0300, Jason Gunthorpe wrote:
> > > On Mon, Oct 16, 2023 at 11:28:15AM +0800, Yi Liu wrote:
> > > > On 2023/10/14 01:56, Nicolin Ch
On Wed, Oct 18, 2023 at 05:40:30PM +0300, Francis Laniel wrote:
> If name_show() is non unique, this test will try to install a kprobe on this
> function which should fail returning EADDRNOTAVAIL.
> On kernel where name_show() is not unique, this test is skipped.
>
> Signed-off-by: Francis Laniel
On Wed, Oct 18, 2023 at 8:08 AM Jeff Xu wrote:
>
> On Tue, Oct 17, 2023 at 9:54 AM Linus Torvalds
> wrote:
> >
> > On Tue, 17 Oct 2023 at 02:08, wrote:
> > >
> > > Of all the call paths that call into do_vmi_munmap(),
> > > this is the only place where checkSeals = MM_SEAL_MUNMAP.
> > > The rest
On Wed, Oct 18, 2023 at 09:30:04AM -0400, Waiman Long wrote:
> On 10/18/23 05:26, Tejun Heo wrote:
> > On Fri, Oct 13, 2023 at 02:11:21PM -0400, Waiman Long wrote:
> > ...
> > > @@ -3875,6 +3931,13 @@ static struct cftype dfl_files[] = {
> > > .flags = CFTYPE_ONLY_ON_ROOT | CFTYPE
On Tue, Oct 17, 2023 at 3:35 PM Pedro Falcato wrote:
>
> > >
> > > I think it's worth pointing out that this suggestion (with PROT_*)
> > > could easily integrate with mmap() and as such allow for one-shot
> > > mmap() + mseal().
> > > If we consider the common case as 'addr = mmap(...); mseal(add
On 10/18/23 14:08, Tejun Heo wrote:
On Wed, Oct 18, 2023 at 09:30:04AM -0400, Waiman Long wrote:
On 10/18/23 05:26, Tejun Heo wrote:
On Fri, Oct 13, 2023 at 02:11:21PM -0400, Waiman Long wrote:
...
@@ -3875,6 +3931,13 @@ static struct cftype dfl_files[] = {
.flags = CFTYPE_ONLY
On Wed, 18 Oct 2023 at 10:14, Jeff Xu wrote:
>
> There is also alternative approach:
>
> For all the places that call do_vmi_munmap(), find out which
> case should ignore the sealing flag legitimately,
NO.
Christ.
THERE ARE NO LEGITIMATE CASES OF IGNORING SEALING FLAGS.
If you ignore a sealing
On Wed, Oct 18, 2023 at 8:17 AM Matthew Wilcox wrote:
>
> Let's start with the purpose. The point of mimmutable/mseal/whatever is
> to fix the mapping of an address range to its underlying object, be it
> a particular file mapping or anonymous memory. After the call succeeds,
> it must not be po
On 10/17/23 17:01, Mark Brown wrote:
The clone3() selftests currently report test results in a format that does
not mesh entirely well with automation. They log output for each test such
as:
# [1382411] Trying clone3() with flags 0 (size 0)
# I am the parent (1382411). My child's pid is 13
On 10/18/23 02:10, Ilpo Järvinen wrote:
On Wed, 18 Oct 2023, Ilpo Järvinen wrote:
Commit 20d96b25cc4c ("selftests/resctrl: Fix schemata write error
check") exposed a problem in feature detection logic in MBM selftest.
If schemata does not support MB:x=x entries, the schemata write to
initialize
On Wed, Oct 18, 2023 at 11:27 AM Linus Torvalds
wrote:
>
> On Wed, 18 Oct 2023 at 10:14, Jeff Xu wrote:
> This is simply not up for discussion. Any flag for "ignore sealing" is wrong.
>
> We do have one special "unmap" case, namely "unmap_vmas()' called at
> last mmput() -> __mmput() -> exit_mmap
On 10/17/23 19:59, zhujun2 wrote:
The opened file should be closed in main(), otherwise resource
leak will occur that this problem was discovered by code reading
Signed-off-by: zhujun2
---
tools/testing/selftests/efivarfs/create-read.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/to
On 10/17/23 09:54, Shuah Khan wrote:
On 10/16/23 20:08, zhujun2 wrote:
when the argument type is 'unsigned int',printf '%u'
in format string
Please add how you found the problem to the commit log.
Signed-off-by: zhujun2
thanks,
-- Shuah
Applied to linux-kselftest next for Linux 6.7-rc
On 10/16/23 15:43, Peter Zijlstra wrote:
On Mon, Oct 16, 2023 at 01:21:20PM -0600, Shuah Khan wrote:
On 10/6/23 03:55, Muhammad Usama Anjum wrote:
Kselftests are kernel tests and must be build with kernel headers from
same source version. The kernel headers are already being included
correctly
On 10/17/23 20:08, Yu Liao wrote:
Yu Liao (2):
selftests/ftrace: add loongarch support for kprobe args char tests
selftests/ftrace: Add riscv support for kprobe arg tests
.../selftests/ftrace/test.d/kprobe/kprobe_args_char.tc | 6 ++
.../selftests/ftrace/test.d/kprobe/kprobe_ar
On 10/18/23 09:41, Waiman Long wrote:
On 10/18/23 05:24, Tejun Heo wrote:
Hello,
On Fri, Oct 13, 2023 at 02:11:19PM -0400, Waiman Long wrote:
When the "isolcpus" boot command line option is used to add a set
of isolated CPUs, those CPUs will be excluded automatically from
wq_unbound_cpumask to
On Fri, Oct 06, 2023, Dongli Zhang wrote:
> As inspired by the discussion in [1], the boottime wallclock may drift due
> to the fact that the masterclock (or host monotonic clock) and kvmclock are
> calculated based on the algorithms in different domains.
>
> This is to introduce a testcase to pri
Jeff Xu wrote:
> On Wed, Oct 18, 2023 at 8:17 AM Matthew Wilcox wrote:
> >
> > Let's start with the purpose. The point of mimmutable/mseal/whatever is
> > to fix the mapping of an address range to its underlying object, be it
> > a particular file mapping or anonymous memory. After the call su
Hi Marco,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.6-rc6 next-20231018]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as doc
On Tue, Oct 17, 2023 at 4:21 PM Nhat Pham wrote:
>
> The interface of list_lru is based on the assumption that objects are
> allocated on the correct node/memcg, with this change it is introduced the
> possibility to explicitly specify numa node and memcgroup when adding and
> removing objects. Th
On Wed, Oct 18, 2023 at 3:27 PM Yosry Ahmed wrote:
>
> On Tue, Oct 17, 2023 at 4:21 PM Nhat Pham wrote:
> >
> > The interface of list_lru is based on the assumption that objects are
> > allocated on the correct node/memcg, with this change it is introduced the
> > possibility to explicitly specif
On Tue, Oct 17, 2023 at 4:21 PM Nhat Pham wrote:
>
> From: Domenico Cerasuolo
>
> Currently, we only have a single global LRU for zswap. This makes it
> impossible to perform worload-specific shrinking - an memcg cannot
> determine which pages in the pool it owns, and often ends up writing
> page
On Tue, Oct 17, 2023 at 4:21 PM Nhat Pham wrote:
>
> From: Domenico Cerasuolo
>
> Since zswap now writes back pages from memcg-specific LRUs, we now need a
> new stat to show writebacks count for each memcg.
>
> Suggested-by: Nhat Pham
> Signed-off-by: Domenico Cerasuolo
> Signed-off-by: Nhat P
On Tue, Oct 17, 2023 at 4:21 PM Nhat Pham wrote:
>
> Currently, we only shrink the zswap pool when the user-defined limit is
> hit. This means that if we set the limit too high, cold data that are
> unlikely to be used again will reside in the pool, wasting precious
> memory. It is hard to predict
On Wed, Oct 18, 2023 at 4:20 PM Yosry Ahmed wrote:
>
> On Tue, Oct 17, 2023 at 4:21 PM Nhat Pham wrote:
> >
> > From: Domenico Cerasuolo
> >
> > Currently, we only have a single global LRU for zswap. This makes it
> > impossible to perform worload-specific shrinking - an memcg cannot
> > determi
On Wed, Oct 18, 2023 at 4:46 PM Nhat Pham wrote:
>
> On Wed, Oct 18, 2023 at 4:20 PM Yosry Ahmed wrote:
> >
> > On Tue, Oct 17, 2023 at 4:21 PM Nhat Pham wrote:
> > >
> > > From: Domenico Cerasuolo
> > >
> > > Currently, we only have a single global LRU for zswap. This makes it
> > > impossible
On Wed, Oct 18, 2023 at 4:25 PM Yosry Ahmed wrote:
>
> On Tue, Oct 17, 2023 at 4:21 PM Nhat Pham wrote:
> >
> > From: Domenico Cerasuolo
> >
> > Since zswap now writes back pages from memcg-specific LRUs, we now need a
> > new stat to show writebacks count for each memcg.
> >
> > Suggested-by: N
On Wed, Oct 18, 2023 at 4:47 PM Nhat Pham wrote:
>
> On Wed, Oct 18, 2023 at 4:20 PM Yosry Ahmed wrote:
> >
> > On Tue, Oct 17, 2023 at 4:21 PM Nhat Pham wrote:
> > >
> > > From: Domenico Cerasuolo
> > >
> > > Currently, we only have a single global LRU for zswap. This makes it
> > > impossible
when the argument type is 'unsigned int',printf '%u'
in format string that this problem was discovered
by code reading
Signed-off-by: zhujun2
---
tools/testing/selftests/kselftest.h | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/tools/testing/selftests/kselft
> From: Jason Gunthorpe
> Sent: Thursday, October 19, 2023 12:51 AM
>
> On Tue, Oct 17, 2023 at 12:58:39PM -0700, Nicolin Chen wrote:
> > On Tue, Oct 17, 2023 at 12:53:01PM -0300, Jason Gunthorpe wrote:
> > > On Tue, Oct 17, 2023 at 08:52:49AM +, Tian, Kevin wrote:
> > > > I prefer to removin
On Wed, Oct 18, 2023 at 12:51:55PM -0700, Sean Christopherson wrote:
> On Fri, Oct 06, 2023, Dongli Zhang wrote:
> > As inspired by the discussion in [1], the boottime wallclock may drift due
> > to the fact that the masterclock (or host monotonic clock) and kvmclock are
> > calculated based on the
44 matches
Mail list logo
