All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	cgroups <cgroups@vger.kernel.org>
Subject: Re: [GIT PULL] cgroup fixes for v4.15-rc7
Date: Mon, 8 Jan 2018 11:23:03 -0800	[thread overview]
Message-ID: <CA+55aFxSbAJe9gnL7jXHUO8KzY8TbrvSt7+jWsTZTJt7EMMzuw@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFzLYgX5WVAFASH65LkTtvSbn_g6eibxe1Psoc1Uc2hFkw@mail.gmail.com>

On Mon, Jan 8, 2018 at 11:20 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Use "strscpy()", which got this _right_.

Oh Christ.

It actually did that initially. And then it was changed to the broken
code due to some idiotic broken warning by tools that don't do the
right thing.

              Linus

  reply	other threads:[~2018-01-08 19:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 14:52 [GIT PULL] cgroup fixes for v4.15-rc7 Tejun Heo
2018-01-08 19:20 ` Linus Torvalds
2018-01-08 19:20   ` Linus Torvalds
2018-01-08 19:23   ` Linus Torvalds [this message]
2018-01-08 19:28     ` Tejun Heo
2018-01-08 19:28       ` Tejun Heo
2018-01-08 19:41       ` Linus Torvalds
2018-01-09 15:21         ` [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup Tejun Heo
2018-01-09 15:21           ` Tejun Heo
2018-01-12 19:38           ` Tejun Heo
2018-01-19 16:50           ` Tejun Heo
2018-01-19 16:50             ` Tejun Heo
2018-01-19 17:27             ` Linus Torvalds
2018-01-19 17:27               ` Linus Torvalds
2018-01-19 17:31               ` Tejun Heo
2018-01-19 17:35                 ` Linus Torvalds
2018-01-19 17:35                   ` Linus Torvalds

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=CA+55aFxSbAJe9gnL7jXHUO8KzY8TbrvSt7+jWsTZTJt7EMMzuw@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=tj@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.