[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a127720d-ed49-5d20-4d63-13da8914652d@redhat.com>
Date: Tue, 20 Sep 2022 10:19:23 +0200
From: David Hildenbrand <david@...hat.com>
To: Akinobu Mita <akinobu.mita@...il.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-kselftest@...r.kernel.org, linux-fsdevel@...r.kernel.org,
corbet@....net, osalvador@...e.de, shuah@...nel.org,
Zhao Gongyi <zhaogongyi@...wei.com>,
Wei Yongjun <weiyongjun1@...wei.com>,
Yicong Yang <yangyicong@...ilicon.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
akpm@...ux-foundation.org
Subject: Re: [PATCH 3/3] debugfs: fix error when writing negative value to
atomic_t debugfs file
On 19.09.22 19:24, Akinobu Mita wrote:
> The simple attribute files do not accept a negative value since the
> commit 488dac0c9237 ("libfs: fix error cast of negative value in
> simple_attr_write()"), so we have to use a 64-bit value to write a
> negative value for a debugfs file created by debugfs_create_atomic_t().
Is that comment stale?
I would ahve thought you simply document that we restore the original
behavior essentially by reverting 005747526d4f ("docs: fault-injection:
fix non-working usage of negative values") and the using
DEFINE_DEBUGFS_ATTRIBUTE_SIGNED accordingly.
>
> This restores the previous behaviour by introducing
> DEFINE_DEBUGFS_ATTRIBUTE_SIGNED for a signed value.
>
> Fixes: 488dac0c9237 ("libfs: fix error cast of negative value in simple_attr_write()")
> Reported-by: Zhao Gongyi <zhaogongyi@...wei.com>
> Signed-off-by: Akinobu Mita <akinobu.mita@...il.com>
Apart from that
Reviewed-by: David Hildenbrand <david@...hat.com>
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists