linux-kernel - Re: [PATCH] mm: fix align-error when get_addr in unmapped_area

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20220507145937.6dbfc036f99addf9342bc5ce@linux-foundation.org>
Date:   Sat, 7 May 2022 14:59:37 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     "lipeifeng@...o.com" <lipeifeng@...o.com>
Cc:     michel <michel@...pinasse.org>, hughd <hughd@...gle.com>,
        linux-mm <linux-mm@...ck.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        "Barry Song" <21cnbao@...il.com>,
        zhangshiming <zhangshiming@...o.com>,
        peifengl55 <peifengl55@...il.com>
Subject: Re: [PATCH] mm: fix align-error when get_addr in
 unmapped_area_topdown

On Mon, 2 May 2022 11:33:18 +0800 "lipeifeng@...o.com" <lipeifeng@...o.com> wrote:

> Hi Andrew：
> 
> Thanks for your quick response.
> 
> > They caused me some merge issues against mapletree, which I had
> > resolved.  Mapletree is dropped at present so I set these patches aside
> > until the next version of the mapletree patches are available.
> 
> Do we have a definite time for the next available version of the mapletree patches?

I merged v2 a couple of days ago.  It should be in mm-unstable then
linux-next early next week.

> Excuse me, is it possible for our patch to be independent of mapletree and brought in separately?

Well, the changelog was rather unclear on the real-world end-user
visible effects of the defect.  When these prioritization decisions are
to be made, it really helps to have a clear view of the impact to our
users.

> 
> > I've been holding your patches until Michel Lespinasse has had time to
> > review them (and hopefully explain them to me ;)).  Please review
> > earlier comments which Michel has provided and ensure that those
> > comments have been fully addressed so we can hopefully move forward on
> > this.
> 
> We will reply soon if Mr.Lespinasse provideds any advices or question.
> And I haven't received any reply from Mr.Lespinasse yet, pls let me know
> if i missed the reply.

There was a big conference last week.