linux-kernel - Re: [Cbe-oss-dev] [patch 11/13] cell: driver for DDR2 memory on AXON

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

Message-Id: <200707191649.27976.arnd@arndb.de>
Date:	Thu, 19 Jul 2007 16:49:27 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Christoph Hellwig <hch@....de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [Cbe-oss-dev] [patch 11/13] cell: driver for DDR2 memory on AXON

On Thursday 19 July 2007, Christoph Hellwig wrote:
> 
> > None of these seems to make any difference whatsoever, except for BLKBSZGET
> > returning non-zero on a ramdisk or dcssblk device. I think we'd be best
> > off removing bd_block_size from the kernel altogether, and I'll remove
> > it from the axon-ram driver now.
> 
> Yes, please.  I even have patches that only pass struct gendisk to block
> device ->open, so this couldn't work anymore anyway.  And yes, the
> ramdisk driver is doing some really odd things.

Any suggestion on what BLKBSZGET should return?

1) blocksize = 0 (same as it does already for most devices)
2) return -EINVAL
3) same as BLKSSZGET
4) return -ENOTTY

It probably doesn't matter much as any user of BLKBSZGET is
already broken, but it would be good to do the right thing
since it is a documented interface.

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