linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Tahsin Erdogan <tahsin@google.com>
Cc: Jan Kara <jack@suse.cz>, Jens Axboe <axboe@kernel.dk>,
	cgroups@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
	Nauman Rafique <nauman@google.com>,
	linux-kernel@vger.kernel.org, Jan Kara <jack@suse.com>
Subject: Re: [PATCH block/for-4.5-fixes] writeback: keep superblock pinned during cgroup writeback association switches
Date: Wed, 17 Feb 2016 18:02:31 -0500	[thread overview]
Message-ID: <20160217230231.GC6479@mtj.duckdns.org> (raw)
In-Reply-To: <CAAeU0aOvSwPbLPU0=20D1RExNj8VsbB38hUnyso2L8xNSQC0XA@mail.gmail.com>

On Wed, Feb 17, 2016 at 02:41:25PM -0800, Tahsin Erdogan wrote:
> With this patch, I am starting to have issues running fsck immediately
> after umount.
> 
> *** fsck.ext4 output ***
> fsck from util-linux-ng 2.17.2
> e2fsck 1.42.12-gg3 (9-Sep-2014)
> Warning!  /dev/sdb3 is in use.
> Pass 1: Checking inodes, blocks, and sizes
> Deleted inode 62346243 has zero dtime.  Fix? no

Yeah, that'd be one of the side effects.  Will think more about it.
Jan, do you know why we have both s_active and the rwsem at this
point?  I can't tell why both are needed.

Thanks.

-- 
tejun

  reply	other threads:[~2016-02-17 23:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAeU0aNCq7LGODvVGRU-oU_o-6enii5ey0p1c26D1ZzYwkDc5A@mail.gmail.com>
     [not found] ` <20160215210047.GN3965@htj.duckdns.org>
     [not found]   ` <CAAeU0aNAd1Ra6LXmWwq8row4MD_BpVHiSXOwHx07m86UWREvHw@mail.gmail.com>
2016-02-16 18:24     ` [PATCH block/for-4.5-fixes] writeback: keep superblock pinned during cgroup writeback association switches Tejun Heo
2016-02-16 18:34       ` Jens Axboe
2016-02-17 20:57       ` Jan Kara
2016-02-17 21:07         ` Tejun Heo
2016-02-17 22:30           ` Jan Kara
2016-02-17 22:41             ` Tahsin Erdogan
2016-02-17 23:02               ` Tejun Heo [this message]
2016-02-18  9:55                 ` Jan Kara
2016-02-18 13:00                   ` Tejun Heo
2016-02-18 13:20                     ` Jan Kara
2016-02-19 20:18                     ` Al Viro
2016-02-19 20:51                       ` Tejun Heo
2016-02-19 21:58                         ` Al Viro
2016-02-19 22:15                           ` Tejun Heo
2016-02-19 22:26                             ` Al Viro
2016-02-28 21:53                               ` Tejun Heo
2016-02-29 20:47                 ` [PATCH block/for-linus] writeback: flush inode cgroup wb switches instead of pinning super_block Tejun Heo
2016-02-29 20:54                   ` Al Viro
2016-02-29 20:58                     ` Tejun Heo
2016-02-29 21:06                       ` Al Viro
2016-02-29 21:08                         ` Tejun Heo
2016-02-29 21:21                           ` Jan Kara
2016-02-29 23:28                   ` [PATCH v2 " Tejun Heo
2016-03-01  9:20                     ` Jan Kara
2016-03-01 17:46                     ` Jens Axboe
2016-03-01 17:50                       ` Tejun Heo
2016-03-02 10:29                         ` Jan Kara
2016-03-01 13:39                   ` [PATCH " Tahsin Erdogan
2016-02-18 10:12       ` [PATCH block/for-4.5-fixes] writeback: keep superblock pinned during cgroup writeback association switches Nikolay Borisov
2016-02-18 12:57         ` Tejun Heo

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=20160217230231.GC6479@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nauman@google.com \
    --cc=tahsin@google.com \
    --cc=tytso@mit.edu \
    /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).