linux-kernel - Re: sysfs binary attribute API flux

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAEwYmTKiC4TcKe=KN4FD_aNAWuoK6HOPCuttbnk-8he5+Dj+Qw@mail.gmail.com>
Date:	Fri, 23 Mar 2012 15:10:56 -0400
From:	Jonathan McCune <jonmccune@....edu>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: sysfs binary attribute API flux

On Fri, Mar 23, 2012 at 12:20 PM, Greg KH <greg@...ah.com> wrote:
> No kernel api is stable, nor will it ever be, see
> Documentation/stable_api_nonsense.txt for details.  As your code is
> living outside of the main kernel.org tree, you will have to deal with
> this for any number of different function calls you make, sysfs is not
> unique at all here.

Thank you.  I think this puts the issue to rest for me.

> Why not just create a new syscall for your work?  That would be easier
> in the longrun, and really, that is what you are doing here.

I may do just that.

Thanks,
-Jon
--
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/