linux-kernel - Re: debugfs_create

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAERLvmRXozQEa2kU=Uo3osGnZuLa-3nZV2-mFNDOiWk5vy2NOg@mail.gmail.com>
Date:	Thu, 14 Aug 2014 11:33:53 +0200
From:	Mattias Nissler <mattias.nissler@....de>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Matt Longnecker <mlongnecker@...dia.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: debugfs_create_{u,x,s}{8,16,32,64}

On Wed, Aug 13, 2014 at 11:57 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Wed, Aug 13, 2014 at 02:57:05PM -0700, Matt Longnecker wrote:
> > Greg,
> >
> > Back in December 2007 Mattias Nissler proposed a patch defining
> > debugfs_create_s32 and friends. In it he reworked the already existent u and
> > x versions. The subject of Mattias's mail was "[PATCH] debugfs: Revamp
> > debugfs_create_{u,x,s}{8,16,32,64} to support signed integers".
> >
> > As I'm writing a new driver related to thermal management, I'm finding the
> > absence of debugfs_create_s32 to be a stumbling block. I see at least two
> > other folks who have stumbled on the absence of debugfs_create_s32 in the
> > past few years.
> >
> > Why didn't we merge Mattias's patch?
>
> I can't remember why I didn't merge a patch from last week, let alone
> from 2007, are you crazy?  :)

Needless to say, I don't remember details either. It might just have
been a case of not adding further debugfs API as long as there's
little demand to justify the addition. The latter may have changed in
the last 7 years (Matt hints at other potential consumers?), but I
personally can't tell as I haven't done any kernel work in more recent
times.

>
>
> > Would you entertain a similar patch today?
>
> I always entertain all patches, you never need to ask if you are allowed
> to send a patch, that's like asking "Am I allowed to ask a question?"...
>
> greg k-h
--
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/