linux-ext4 - Re: [PATCH] ext4: Add support for FIDTRIM, a best-effort ioctl for deep discard trim

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKP4w2TzDu6d=hK+21GnZU6Sd_gH8icJ=XA3q23Oa9Bd9fF6uA@mail.gmail.com>
Date:	Thu, 24 Jul 2014 18:50:22 -0700
From:	JP Abgrall <jpa@...gle.com>
To:	Dave Chinner <david@...morbit.com>
Cc:	linux-ext4@...r.kernel.org,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	Geremy Condra <gcondra@...gle.com>
Subject: Re: [PATCH] ext4: Add support for FIDTRIM, a best-effort ioctl for
 deep discard trim

On Thu, Jul 24, 2014 at 5:08 AM, Dave Chinner <david@...morbit.com> wrote:
>
> On Wed, Jul 23, 2014 at 04:47:18PM -0700, JP Abgrall wrote:
> > +#define FIDTRIM      _IOWR('X', 122, struct fstrim_range)    /* Deep discard trim */
>
> The 'X' ioctl namespace is actually XFS's ioctl namespace. FIDTRIM
> should be in the 'f' namespace
Ok.
How should the next sequence number be handled?
Go with ('f', 122,...) after FITRIM, or go with ('f', 12,...) after
FS_IOC_FIEMAP ('f' namepsace)?
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html