[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200424234647.GX6749@magnolia>
Date: Fri, 24 Apr 2020 16:46:47 -0700
From: "Darrick J. Wong" <darrick.wong@...cle.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: Ritesh Harjani <riteshh@...ux.ibm.com>,
Eric Biggers <ebiggers@...nel.org>,
linux-fsdevel@...r.kernel.org, linux-xfs@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
Christoph Hellwig <hch@...radead.org>,
Jan Kara <jack@...e.com>, tytso@....edu,
"Aneesh Kumar K . V" <aneesh.kumar@...ux.ibm.com>,
linux-ext4@...r.kernel.org
Subject: Re: [PATCH 1/2] fibmap: Warn and return an error in case of block >
INT_MAX
On Fri, Apr 24, 2020 at 04:40:58PM -0700, Matthew Wilcox wrote:
> On Sat, Apr 25, 2020 at 04:24:24AM +0530, Ritesh Harjani wrote:
> > Ok, I see.
> > Let me replace WARN() with below pr_warn() line then. If no objections,
> > then will send this in a v2 with both patches combined as Darrick
> > suggested. - (with Reviewed-by tags of Jan & Christoph).
> >
> > pr_warn("fibmap: this would truncate fibmap result\n");
>
> We generally don't like userspace to be able to trigger kernel messages
> on demand, so they can't swamp the logfiles. printk_ratelimited()?
Or WARN_ON_ONCE...
--D
Powered by blists - more mailing lists