public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Kees Cook <keescook@chromium.org>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	dm-devel@redhat.com, Dan Williams <dan.j.williams@intel.com>,
	Alasdair Kergon <agk@redhat.com>
Subject: Re: dm: writecache: Use 2-factor allocator arguments
Date: Wed, 27 Jun 2018 17:52:27 -0400	[thread overview]
Message-ID: <20180627215227.GA13549@redhat.com> (raw)
In-Reply-To: <CAGXu5j+Su3fObnuzntQ7Tp8W6jfMt1hc=h-3Xhidgx--Nau1Ew@mail.gmail.com>

On Wed, Jun 27 2018 at  5:48pm -0400,
Kees Cook <keescook@chromium.org> wrote:

> On Mon, Jun 18, 2018 at 10:50 AM, Kees Cook <keescook@chromium.org> wrote:
> > This adjusts the allocator calls to use the 2-factor argument style, as
> > already done treewide for better defense against allocator overflows.
> > Additionally adjusts style nit to avoid assignments in test expressions.
> >
> > Signed-off-by: Kees Cook <keescook@chromium.org>
> 
> Friendly ping -- I'd like to make sure this makes it into 4.18. All
> other 2-factor allocations have been fixed in the kernel.

Yeap, I'll be sending it to Linus this week.  Already staged and ready
to go, please see:
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.18&id=50a7d3ba7c9ac5e0b7e03fc7f420180989361dbf

Thanks,
Mike

  reply	other threads:[~2018-06-27 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 17:50 [PATCH] dm: writecache: Use 2-factor allocator arguments Kees Cook
2018-06-18 21:12 ` Mikulas Patocka
2018-06-18 22:10   ` Kees Cook
2018-06-27 21:48 ` Kees Cook
2018-06-27 21:52   ` Mike Snitzer [this message]
2018-06-27 21:53     ` Kees Cook

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=20180627215227.GA13549@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=dm-devel@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    /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