Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <20181109151520.GD3645@cisco>
References: <20181102201822.12518-1-tycho@tycho.ws> <20181107222042.GA24927@redhat.com>
 <20181109151520.GD3645@cisco>
From:   Kees Cook <keescook@chromium.org>
Date:   Thu, 15 Nov 2018 12:24:58 -0600
Message-ID: <CAGXu5jLEjLyp+nNd1f-m+NZa+KVW5DNC+kD2zqubddzAM7aVdA@mail.gmail.com>
Subject: Re: [PATCH 0/3] dlm: fix various incorrect behaviors
To:     Tycho Andersen <tycho@tycho.ws>
Cc:     David Teigland <teigland@redhat.com>,
        Christine Caulfield <ccaulfie@redhat.com>,
        cluster-devel@redhat.com, LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Nov 9, 2018 at 9:15 AM, Tycho Andersen <tycho@tycho.ws> wrote:
> On Wed, Nov 07, 2018 at 04:20:42PM -0600, David Teigland wrote:
>> On Fri, Nov 02, 2018 at 02:18:19PM -0600, Tycho Andersen wrote:
>> > Hi,
>> >
>> > here's a series to fix some bugs I noticed in the DLM. The third patch
>> > in the series and maybe the first should probably go to stable, assuming
>> > everyone agrees they're indeed bugs.
>> >
>> > Thanks,
>> >
>> > Tycho
>> >
>> > Tycho Andersen (3):
>> >   dlm: fix invalid free
>> >   dlm: don't allow zero length names
>> >   dlm: don't leak kernel pointer to userspace
>> >
>> >  fs/dlm/lockspace.c | 2 +-
>> >  fs/dlm/member.c    | 5 +++--
>> >  fs/dlm/user.c      | 2 +-
>> >  3 files changed, 5 insertions(+), 4 deletions(-)
>>
>> I've pushed these to linux-dlm next.
>
> Great, thanks! Should we send 1 and 3 to stable?

Yes please! :)

-- 
Kees Cook