linux-kernel - Re: [PATCH] null_blk: use sector_div instead of do

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: <4333086.QZV0XpURJu@wuerfel>
Date:	Wed, 13 Jan 2016 22:46:30 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	Matias Bjørling <m@...rling.me>,
	Jens Axboe <axboe@...com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] null_blk: use sector_div instead of do_div

On Friday 18 December 2015 17:13:40 Arnd Bergmann wrote:
> On Saturday 28 November 2015 09:05:56 Matias Bjørling wrote:
> > 
> > I had my head around the original code and kept references to the device 
> > layout I had in mind. 256 being number of pages in a block, and the 2^16 
> > being number of blocks in a lun and wanted to communicate that part.. 
> > which led to producing silly code in the mean time.
> > 
> > Similarly, the bs is always fixed to 4k for lightnvm, until other bs 
> > sizes are supported. We could optimize it out, I left it in for the same 
> > reasons.
> 
> I still see the build warning in linux-next, can you merge your patch?

The merge window is open now, the bug persists in linux-next. I'm
submitting Matias version now.

	Arnd