linux-ext4 - Re: Potential bug in mballoc --- reusing data blocks before txn commit

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: <48E15F4D.3000305@redhat.com>
Date:	Mon, 29 Sep 2008 19:05:49 -0400
From:	Ric Wheeler <rwheeler@...hat.com>
To:	Theodore Tso <tytso@....edu>
CC:	Ric Wheeler <rwheeler@...hat.com>, Alex Tomas <bzzz@....com>,
	Andreas Dilger <adilger@....com>, linux-ext4@...r.kernel.org
Subject: Re: Potential bug in mballoc --- reusing data blocks before txn commit

Theodore Tso wrote:
> On Mon, Sep 29, 2008 at 05:04:04PM -0400, Ric Wheeler wrote:
>   
>> I don't disagree with any of the above, just want to point out that TRIM  
>> has a  SCSI T10 cousin that is very similar (used to implement thinly  
>> provisioned luns). We should make sure as much as possible to make our  
>> file system level support work for both...
>>
>>     
>
> That's shouldn't be a problem.  David Woodhouse created a standard
> block device interface that should be suitable both for ATA and SCSI:
>
>     int blkdev_issue_discard(struct block_device *bdev, sector_t sector,
> 		         unsigned nr_sects, bio_end_io_t end_io);
>
> 							- Ted
>
>   

I know, just wanted to point out to the broader audience that it is not 
just trim ;-)

ric

--
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