[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zrmt01OTCRywW55v@infradead.org>
Date: Sun, 11 Aug 2024 23:38:11 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Martin Oliveira <martin.oliveira@...eticom.com>,
linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
Artemy Kovalyov <artemyko@...dia.com>,
Jason Gunthorpe <jgg@...pe.ca>, Leon Romanovsky <leon@...nel.org>,
Logan Gunthorpe <logang@...tatee.com>,
Michael Guralnik <michaelgur@...dia.com>,
Mike Marciniszyn <mike.marciniszyn@...el.com>,
Shiraz Saleem <shiraz.saleem@...el.com>, Tejun Heo <tj@...nel.org>,
John Hubbard <jhubbard@...dia.com>,
Dan Williams <dan.j.williams@...el.com>,
David Sloan <david.sloan@...eticom.com>
Subject: Re: [PATCH v5 1/4] kernfs: add a WARN_ON_ONCE if ->close is set
On Fri, Aug 09, 2024 at 07:37:49AM +0200, Greg Kroah-Hartman wrote:
> > * It is not possible to successfully wrap close.
> > * So error if someone is trying to use close.
> > */
> > - if (vma->vm_ops && vma->vm_ops->close)
> > + if (WARN_ON_ONCE(vma->vm_ops && vma->vm_ops->close))
>
> So you just rebooted a machine that hits this, loosing data everywhere.
> Not nice :(
Huh. if you are stupid enough to set panic_on_warn you get to keep
the pieces. And our file systems are reliable to not use data on
an unclean shutdown anyway.
Pleaee stop these BS arguments.
Powered by blists - more mailing lists