linux-kernel - The question about blkdev_issue_discard and discard

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

Message-ID: <CANaxB-zpcuxeJ7TSi+3DbaFE=-FUH31c=sUg72bdBCdBnRANaQ@mail.gmail.com>
Date:	Thu, 22 Mar 2012 17:04:07 +0400
From:	Andrew Wagin <avagin@...il.com>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	linux-kernel@...r.kernel.org
Subject: The question about blkdev_issue_discard and discard_granularity

Hello Jens,

I'm developing a virtual disk (aka ploop). Now I'm adding support of
discard requests. A block size of ploop may be customized, so I want
that a discard request contains only whole blocks. I found a queue's
parameter discard_granularity and set it correctly, but nothing's
changed. A kernel continues sending bio with size smaller than
discard_granularity and with unaligned borders.

I found that max_discard_sectors is aligned according with discard_granularity.

Why are bi->bi_size and bi->bi_sector not aligned according with
discard_granularity?

If it's just because nobody did this, I can do.

Thanks,
Andrey
--
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/