On 9/21/18 1:25 AM, Ming Lei wrote: > On Fri, Sep 21, 2018 at 09:08:05AM +0200, Christoph Hellwig wrote: >> On Fri, Sep 21, 2018 at 11:56:08AM +1000, Dave Chinner wrote: >>>> 3) If slab can't guarantee to return 512-aligned buffer, how to fix >>>> this data corruption issue? >>> >>> I think that the block layer needs to check the alignment of memory >>> buffers passed to it and take appropriate action rather than >>> corrupting random memory and returning a sucess status to the bad >>> bio. >> >> Or just reject the I/O. But yes, we already have the >> queue_dma_alignment helper in the block layer, we just don't do it >> in the fast path. I think generic_make_request_checks needs to >> check it, and print an error and return a warning if the alignment >> requirement isn't met. > > That can be done in generic_make_request_checks(), but some cost may be > introduced, because each bvec needs to be checked in the fast path. I think this is all crazy talk. We've never done this, we've always assumed that an address of length N, will be N aligned as well. If a driver sets queue dma alignment > than its sector size, then we're in real trouble and would need to bounce IOs. That's silly enough that it doesn't warrant being done in the core code imho, if you're hw is that crappy, then do it in your queue_rq(). Could be done with a core helper for sure, but I'm really not that interested in having a full bvec loop for each bio just to check something that (to my knowledge) hasn't been an issue in decades. -- Jens Axboe
