public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk
Cc: peterz@infradead.org, willy@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] A couple of i_dir_seq fixes for fs/dcache.c
Date: Mon, 26 Feb 2018 18:05:48 +0000	[thread overview]
Message-ID: <20180226180547.GL26147@arm.com> (raw)
In-Reply-To: <1519052155-6361-1-git-send-email-will.deacon@arm.com>

H Al,

On Mon, Feb 19, 2018 at 02:55:53PM +0000, Will Deacon wrote:
> This is version two of the patch I previously posted here:
> 
>   http://lkml.kernel.org/r/1518526731-26546-1-git-send-email-will.deacon@arm.com
> 
> Changes since v1:
> 
>   * Added READ_ONCE to i_dir_seq access
>   * Added tags
> 
> Cheers,
> 
> Will
> 
> --->8
> 
> Will Deacon (2):
>   fs: dcache: Avoid livelock between d_alloc_parallel and __d_add
>   fs: dcache: Use READ_ONCE when accessing i_dir_seq
> 
>  fs/dcache.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)

Is there anything more you need from me on this series? I don't see it
queued anywhere and we're seeing this livelock hitting us in practice.

Cheers,

Will

      parent reply	other threads:[~2018-02-26 18:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 14:55 [PATCH v2 0/2] A couple of i_dir_seq fixes for fs/dcache.c Will Deacon
2018-02-19 14:55 ` [PATCH v2 1/2] fs: dcache: Avoid livelock between d_alloc_parallel and __d_add Will Deacon
2018-02-19 14:55 ` [PATCH v2 2/2] fs: dcache: Use READ_ONCE when accessing i_dir_seq Will Deacon
2018-02-26 18:05 ` Will Deacon [this message]

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=20180226180547.GL26147@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox