On Thu, Oct 17, 2024 at 12:14 PM Pedro Falcato wrote:
>
> On Thu, Oct 17, 2024 at 09:20:20AM -0700, Jeff Xu wrote:
> > On Thu, Oct 17, 2024 at 1:18 AM Lorenzo Stoakes
> > wrote:
> > >
> > > NACK. Greg's bot got to it but...
> > >
> > > As per Greg's bot, no signed-off-by line.
> > >
> > Sorry for
On Thu, Oct 17, 2024 at 08:14:11PM +0100, Pedro Falcato wrote:
> On Thu, Oct 17, 2024 at 09:20:20AM -0700, Jeff Xu wrote:
> > On Thu, Oct 17, 2024 at 1:18 AM Lorenzo Stoakes
> > wrote:
> > >
> > > NACK. Greg's bot got to it but...
> > >
> > > As per Greg's bot, no signed-off-by line.
> > >
> > Sor
On Thu, Oct 17, 2024 at 09:20:20AM -0700, Jeff Xu wrote:
> On Thu, Oct 17, 2024 at 1:18 AM Lorenzo Stoakes
> wrote:
> >
> > NACK. Greg's bot got to it but...
> >
> > As per Greg's bot, no signed-off-by line.
> >
> Sorry for confusion, I wasn't meant to send this as a PATCH, but
> reporting the iss
On Thu, Oct 17, 2024 at 1:18 AM Lorenzo Stoakes
wrote:
>
> NACK. Greg's bot got to it but...
>
> As per Greg's bot, no signed-off-by line.
>
Sorry for confusion, I wasn't meant to send this as a PATCH, but
reporting the issue.
The diff was just sent as reference to repro the bug, and I forgot to
r
On Wed, Oct 16, 2024 at 11:04 PM Greg KH wrote:
>
> On Thu, Oct 17, 2024 at 02:26:27AM +, jef...@chromium.org wrote:
> > From: Jeff Xu
> >
> > It appears there is a regression on the latest mm,
> > when munmap sealed memory, it can cause unexpected VMA split.
> > E.g. repro use this test.
> >
OK having said all of the below I think I know exactly what this is...
When an munmap() operation aborts due to error it does not attempt to
re-merge previously split VMAs so you might observe more splits than you
expect.
This is not a bug, it's expected behaviour. We do intend to address this
go
On Thu, Oct 17, 2024 at 10:46:10AM +0100, Lorenzo Stoakes wrote:
[snip]
> Anyway, let's try to decode (please take this as input as to how you should
> try to communicate these things):
>
>
> So we start with a VMA like this:
>
> 012345678901
>
>
> We then seal the middle, starting at
Another thing about etiquette - sending a barely coherent _failing_ test
with basically zero explanation as a... patch is NOT how to interact with
the upstream community.
The sensible, respectful and workable way of doing this is to send
something like a [DISCUSSION] or something and say 'hey guys
NACK. Greg's bot got to it but...
As per Greg's bot, no signed-off-by line.
The subject should be something about adding a test.
You later say you are somehow dependning on things (what?) to make this work but
it's broken.
Jeff - you're doing things that were raised on previous reviews as if we
On Thu, Oct 17, 2024 at 02:26:27AM +, jef...@chromium.org wrote:
> From: Jeff Xu
>
> It appears there is a regression on the latest mm,
> when munmap sealed memory, it can cause unexpected VMA split.
> E.g. repro use this test.
> ---
> tools/testing/selftests/mm/mseal_test.c | 76 +++
On Wed, Oct 16, 2024 at 7:26 PM wrote:
>
> From: Jeff Xu
>
> It appears there is a regression on the latest mm,
> when munmap seals memory, it can cause an unexpected VMA split.
> E.g. repro use this test.
It appears that this test has some dependency tests that haven't been
merged, so can't be
From: Jeff Xu
It appears there is a regression on the latest mm,
when munmap sealed memory, it can cause unexpected VMA split.
E.g. repro use this test.
---
tools/testing/selftests/mm/mseal_test.c | 76 +
1 file changed, 76 insertions(+)
diff --git a/tools/testing/selfte
12 matches
Mail list logo
