From: Kees Cook <keescook@chromium.org>
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>
Subject: Re: [PATCH 0/3] dlm: fix various incorrect behaviors
Date: Thu, 15 Nov 2018 12:24:58 -0600 [thread overview]
Message-ID: <CAGXu5jLEjLyp+nNd1f-m+NZa+KVW5DNC+kD2zqubddzAM7aVdA@mail.gmail.com> (raw)
In-Reply-To: <20181109151520.GD3645@cisco>
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
prev parent reply other threads:[~2018-11-15 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 20:18 [PATCH 0/3] dlm: fix various incorrect behaviors Tycho Andersen
2018-11-02 20:18 ` [PATCH 1/3] dlm: fix invalid free Tycho Andersen
2018-11-02 20:18 ` [PATCH 2/3] dlm: don't allow zero length names Tycho Andersen
2018-11-02 20:18 ` [PATCH 3/3] dlm: don't leak kernel pointer to userspace Tycho Andersen
2018-11-07 22:20 ` [PATCH 0/3] dlm: fix various incorrect behaviors David Teigland
2018-11-09 15:15 ` Tycho Andersen
2018-11-15 18:24 ` Kees Cook [this message]
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=CAGXu5jLEjLyp+nNd1f-m+NZa+KVW5DNC+kD2zqubddzAM7aVdA@mail.gmail.com \
--to=keescook@chromium.org \
--cc=ccaulfie@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=teigland@redhat.com \
--cc=tycho@tycho.ws \
/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;
as well as URLs for NNTP newsgroup(s).