From: Andrew Morton <akpm@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
syzbot+fb77e97ebf0612ee6914@syzkaller.appspotmail.com,
Alexander Viro <viro@zeniv.linux.org.uk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm: Limit to INT_MAX in create_blob ioctl
Date: Wed, 6 Nov 2019 10:13:49 -0800 [thread overview]
Message-ID: <20191106101349.7dfaa4282db4c7a0239b96f2@linux-foundation.org> (raw)
In-Reply-To: <201911060920.71D7E76E@keescook>
On Wed, 6 Nov 2019 09:24:18 -0800 Kees Cook <keescook@chromium.org> wrote:
> > Since this is -mm can I have a stable sha1 or something for
> > referencing? Or do you want to include this in the -mm patch bomb for
> > the merge window?
>
> Traditionally these things live in akpm's tree when they are fixes for
> patches in there. I have no idea how the Fixes tags work in that case,
> though...
I queued it immediately ahead of
uaccess-disallow-int_max-copy-sizes.patch so all should be good,
thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
syzbot+fb77e97ebf0612ee6914@syzkaller.appspotmail.com,
Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm: Limit to INT_MAX in create_blob ioctl
Date: Wed, 6 Nov 2019 10:13:49 -0800 [thread overview]
Message-ID: <20191106101349.7dfaa4282db4c7a0239b96f2@linux-foundation.org> (raw)
Message-ID: <20191106181349.7ghDqJbceo19uj45ho2z0G_s7c_4d7qyS15moOSTxXg@z> (raw)
In-Reply-To: <201911060920.71D7E76E@keescook>
On Wed, 6 Nov 2019 09:24:18 -0800 Kees Cook <keescook@chromium.org> wrote:
> > Since this is -mm can I have a stable sha1 or something for
> > referencing? Or do you want to include this in the -mm patch bomb for
> > the merge window?
>
> Traditionally these things live in akpm's tree when they are fixes for
> patches in there. I have no idea how the Fixes tags work in that case,
> though...
I queued it immediately ahead of
uaccess-disallow-int_max-copy-sizes.patch so all should be good,
thanks.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-06 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 16:47 [PATCH] drm: Limit to INT_MAX in create_blob ioctl Daniel Vetter
2019-11-06 16:47 ` Daniel Vetter
2019-11-06 17:03 ` Ville Syrjälä
2019-11-06 17:03 ` Ville Syrjälä
2019-11-06 17:24 ` Kees Cook
2019-11-06 17:24 ` Kees Cook
2019-11-06 17:56 ` Daniel Vetter
2019-11-06 17:56 ` Daniel Vetter
2019-11-06 18:13 ` Andrew Morton [this message]
2019-11-06 18:13 ` Andrew Morton
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=20191106101349.7dfaa4282db4c7a0239b96f2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+fb77e97ebf0612ee6914@syzkaller.appspotmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).