From: Willy Tarreau <w@1wt.eu>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 3.10 14/46] d_walk() might skip too much
Date: Sat, 13 Jun 2015 19:11:18 +0200 [thread overview]
Message-ID: <20150613171118.GB13001@1wt.eu> (raw)
In-Reply-To: <CACMCwJ+0JhuoUgh2sEnJoZ3PGvwGoE6_WFOP4KbXsprirfSFWQ@mail.gmail.com>
Hi Jari,
On Sat, Jun 13, 2015 at 07:01:31PM +0300, Jari Ruusu wrote:
> When Al Viro's VFS deadlock fix "deal with deadlock in d_walk()" was
> backported to 3.10.y 3.4.y and 3.2.y stable kernel brances, the deadlock fix
> was copied to 3 different places. Later, a bug in that code was discovered.
> Al Viro's fix involved fixing only one part of code in mainline kernel. That
> fix is called "d_walk() might skip too much".
>
> 3.10.y 3.4.y and 3.2.y stable kernel brances need that later fix copied to 3
> different places. Greg Kroah-Hartman included Al Viro's "d_walk() might skip
> too much" fix only once in 3.10.80 kernel, leaving 2 more places without a
> fix.
>
> The patch below was not written by me. I only applied Al Viro's "d_walk()
> might skip too much" fix 2 more times to 3.10.80 kernel, and cheched that
> the fixes went to correct places. With this patch applied, all 3 places that
> I am aware of 3.10.y stable branch are now fixed.
>
> Signed-off-by: Jari Ruusu <jariruusu@users.sourceforge.net>
Next time, please don't forget to mention the mainline commit IDs in
addition to the message subjects, it helps a lot. The IDs from the
stable branches are less important since it's generally quite easy
to find them thanks to the mainline ID which appears in the message.
Just for reference :
- ca5358e ("deal with deadlock in d_walk()")
- 2159184 ("d_walk() might skip too much")
Thanks,
Willy
next prev parent reply other threads:[~2015-06-13 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 15:01 Jari Ruusu
2015-06-13 16:01 ` Jari Ruusu
2015-06-13 17:11 ` Willy Tarreau [this message]
2015-06-19 19:54 ` Greg Kroah-Hartman
2015-06-20 7:41 ` Jari Ruusu
2015-06-27 0:52 ` Greg Kroah-Hartman
2015-06-27 5:56 ` Willy Tarreau
2015-06-30 0:37 ` Greg Kroah-Hartman
2015-06-28 8:56 ` Jari Ruusu
-- strict thread matches above, loose matches on Subject: below --
2015-06-03 11:42 [PATCH 3.10 00/46] 3.10.80-stable review Greg Kroah-Hartman
2015-06-03 11:42 ` [PATCH 3.10 14/46] d_walk() might skip too much Greg Kroah-Hartman
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=20150613171118.GB13001@1wt.eu \
--to=w@1wt.eu \
--cc=gregkh@linuxfoundation.org \
--cc=jariruusu@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®