[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150708081248.GA725@quack.suse.cz>
Date: Wed, 8 Jul 2015 10:12:49 +0200
From: Jan Kara <jack@...e.cz>
To: Tejun Heo <tj@...nel.org>
Cc: Jan Kara <jack@...e.cz>, axboe@...nel.dk,
linux-kernel@...r.kernel.org, hch@...radead.org,
hannes@...xchg.org, linux-fsdevel@...r.kernel.org,
vgoyal@...hat.com, lizefan@...wei.com, cgroups@...r.kernel.org,
linux-mm@...ck.org, mhocko@...e.cz, clm@...com,
fengguang.wu@...el.com, david@...morbit.com, gthelen@...gle.com,
khlebnikov@...dex-team.ru
Subject: Re: [PATCH block/for-4.3] writeback: explain why @inode is allowed
to be NULL for inode_congested()
On Sat 04-07-15 11:12:00, Tejun Heo wrote:
> Signed-off-by: Tejun Heo <tj@...nel.org>
> Suggested-by: Jan Kara <jack@...e.cz>
> ---
> Hello,
>
> So, something like this. I'll resend this patch as part of a patch
> series once -rc1 drops.
Looks good. Thanks!
Honza
> fs/fs-writeback.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -700,7 +700,7 @@ void wbc_account_io(struct writeback_con
>
> /**
> * inode_congested - test whether an inode is congested
> - * @inode: inode to test for congestion
> + * @inode: inode to test for congestion (may be NULL)
> * @cong_bits: mask of WB_[a]sync_congested bits to test
> *
> * Tests whether @inode is congested. @cong_bits is the mask of congestion
> @@ -710,6 +710,9 @@ void wbc_account_io(struct writeback_con
> * determined by whether the cgwb (cgroup bdi_writeback) for the blkcg
> * associated with @inode is congested; otherwise, the root wb's congestion
> * state is used.
> + *
> + * @inode is allowed to be NULL as this function is often called on
> + * mapping->host which is NULL for the swapper space.
> */
> int inode_congested(struct inode *inode, int cong_bits)
> {
--
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists