linux-kernel - Re: [PATCHv3 9/9] zram: add dynamic device add/remove functionality

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

Message-ID: <20150429072328.GA2987@swordfish>
Date:	Wed, 29 Apr 2015 16:23:28 +0900
From:	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To:	Minchan Kim <minchan@...nel.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Nitin Gupta <ngupta@...are.org>, linux-kernel@...r.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: [PATCHv3 9/9] zram: add dynamic device add/remove functionality

On (04/29/15 16:02), Sergey Senozhatsky wrote:
> sure. I was talking about this one:
> 
> 	CPU0			CPU1
> 	umount
> 	zram_remove()
> 	lock ->bd_mutex
> 	zram_reset_device()
> 	unlock ->bd_mutex
> 				disksize_store
> 				mount
> 				echo 'test' > /mnt/test
> 	kfree zram
> 				zram write
> 

I'll take a look later today. currently I think of something like:


	sysfs_remove_group()
	lock ->bd_mutex
		... check ->bd_openers

	zram_reset_device()
	blk_cleanup_queue()
	del_gendisk()
	put_disk()

	unlock ->bd_mutex
	bdput bdev

	idr_remove()
	kfree(zram)


iow, idr_remove() and kfree() are done outside of ->bd_mutex lock.
but I may be wrong. haven't tested yet. but seems reasonable: we
invalidate ->bdev, delete partitions, etc., holding ->bd_mutex and
then release ->bdev, which does final put. need to check that in
detail.

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