From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Sedat Dilek <sedat.dilek-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] sysctl fixes for v4.13-rc1
Date: Thu, 13 Jul 2017 04:28:29 -0500 [thread overview]
Message-ID: <87r2xkeldu.fsf@xmission.com> (raw)
In-Reply-To: <CA+icZUUK8M3dwj9ns8951bzTcQ+-0Uo2r_6PDdeMX5XUq_VAsg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Sedat Dilek's message of "Thu, 13 Jul 2017 09:47:01 +0200")
Sedat Dilek <sedat.dilek-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> On Thu, Jul 13, 2017 at 2:45 AM, Eric W. Biederman
> <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org> wrote:
>>
>> Linus,
>>
>> Please pull the for-linus branch from the git tree:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus
>>
>> HEAD: 2fd1d2c4ceb2248a727696962cf3370dc9f5a0a4 proc: Fix proc_sys_prune_dcache to hold a sb reference
>>
>> A rather embarassing and hard to hit bug was merged into 4.11-rc1.
>> Andrei Vagin tracked this bug now and after some starting at the
>> code I came up with a fix.
>>
>> Eric
>>
>> From 2fd1d2c4ceb2248a727696962cf3370dc9f5a0a4 Mon Sep 17 00:00:00 2001
>> From: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
>> Date: Thu, 6 Jul 2017 08:41:06 -0500
>> Subject: [PATCH] proc: Fix proc_sys_prune_dcache to hold a sb reference
>>
>> Andrei Vagin writes:
>> FYI: This bug has been reproduced on 4.11.7
> [...]
>
>> Cc: stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>
> Please add first affected Linux-kernel release.
>
> Cc: stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org # 4.11
Please look at the fixes tags below. Especially when changes are
backported that seems to be a much better indicator of what is
affected than some arbitrary kernel number.
I have included a Fixes tags for the originally buggy commit and
a Fixes tag for the incomplete fix for the originally buggy commit.
As a rule I only include a kernel version number if the originally
affected kernel is not in Linus's git tree, and not in Thomas's
conversion of the original bitkeeper tree to git.
>
> - Sedat -
>
>> Reported-by: Andrei Vagin <avagin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Tested-by: Andrei Vagin <avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
>> Fixes: ace0c791e6c3 ("proc/sysctl: Don't grab i_lock under sysctl_lock.")
>> Fixes: d6cffbbe9a7e ("proc/sysctl: prune stale dentries during unregistering")
>> Signed-off-by: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Linux Containers <containers@lists.linux-foundation.org>,
linux-fsdevel@vger.kernel.org, Andrei Vagin <avagin@gmail.com>
Subject: Re: [GIT PULL] sysctl fixes for v4.13-rc1
Date: Thu, 13 Jul 2017 04:28:29 -0500 [thread overview]
Message-ID: <87r2xkeldu.fsf@xmission.com> (raw)
In-Reply-To: <CA+icZUUK8M3dwj9ns8951bzTcQ+-0Uo2r_6PDdeMX5XUq_VAsg@mail.gmail.com> (Sedat Dilek's message of "Thu, 13 Jul 2017 09:47:01 +0200")
Sedat Dilek <sedat.dilek@gmail.com> writes:
> On Thu, Jul 13, 2017 at 2:45 AM, Eric W. Biederman
> <ebiederm@xmission.com> wrote:
>>
>> Linus,
>>
>> Please pull the for-linus branch from the git tree:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus
>>
>> HEAD: 2fd1d2c4ceb2248a727696962cf3370dc9f5a0a4 proc: Fix proc_sys_prune_dcache to hold a sb reference
>>
>> A rather embarassing and hard to hit bug was merged into 4.11-rc1.
>> Andrei Vagin tracked this bug now and after some starting at the
>> code I came up with a fix.
>>
>> Eric
>>
>> From 2fd1d2c4ceb2248a727696962cf3370dc9f5a0a4 Mon Sep 17 00:00:00 2001
>> From: "Eric W. Biederman" <ebiederm@xmission.com>
>> Date: Thu, 6 Jul 2017 08:41:06 -0500
>> Subject: [PATCH] proc: Fix proc_sys_prune_dcache to hold a sb reference
>>
>> Andrei Vagin writes:
>> FYI: This bug has been reproduced on 4.11.7
> [...]
>
>> Cc: stable@vger.kernel.org
>
> Please add first affected Linux-kernel release.
>
> Cc: stable@vger.kernel.org # 4.11
Please look at the fixes tags below. Especially when changes are
backported that seems to be a much better indicator of what is
affected than some arbitrary kernel number.
I have included a Fixes tags for the originally buggy commit and
a Fixes tag for the incomplete fix for the originally buggy commit.
As a rule I only include a kernel version number if the originally
affected kernel is not in Linus's git tree, and not in Thomas's
conversion of the original bitkeeper tree to git.
>
> - Sedat -
>
>> Reported-by: Andrei Vagin <avagin@gmail.com>
>> Tested-by: Andrei Vagin <avagin@openvz.org>
>> Fixes: ace0c791e6c3 ("proc/sysctl: Don't grab i_lock under sysctl_lock.")
>> Fixes: d6cffbbe9a7e ("proc/sysctl: prune stale dentries during unregistering")
>> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Eric
next prev parent reply other threads:[~2017-07-13 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 0:45 [GIT PULL] sysctl fixes for v4.13-rc1 Eric W. Biederman
2017-07-13 0:45 ` Eric W. Biederman
[not found] ` <87d195f9m7.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2017-07-13 7:47 ` Sedat Dilek
2017-07-13 7:47 ` Sedat Dilek
[not found] ` <CA+icZUUK8M3dwj9ns8951bzTcQ+-0Uo2r_6PDdeMX5XUq_VAsg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-13 9:28 ` Eric W. Biederman [this message]
2017-07-13 9:28 ` Eric W. Biederman
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=87r2xkeldu.fsf@xmission.com \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sedat.dilek-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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.