All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	James Bottomley <JBottomley@Parallels.com>,
	Namjae Jeon <namjae.jeon@samsung.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] block: fix max discard sectors limit
Date: Wed, 24 Apr 2013 08:23:32 -0600	[thread overview]
Message-ID: <20130424142332.GD2759@kernel.dk> (raw)
In-Reply-To: <1366811721-2478-1-git-send-email-linkinjeon@gmail.com>

On Wed, Apr 24 2013, Namjae Jeon wrote:
> From: James Bottomley <JBottomley@Parallels.com>
> 
> linux-v3.8-rc1 and later support for plug for blkdev_issue_discard with
> commit 0cfbcafcae8b7364b5fa96c2b26ccde7a3a296a9
> (block: add plug for blkdev_issue_discard )
> 
> For example,
> 1) DISCARD rq-1 with size size 4GB
> 2) DISCARD rq-2 with size size 1GB
> 
> If these 2 discard requests get merged, final request size will be 5GB.
> 
> In this case, request's __data_len field may overflow as it can store
> max 4GB(unsigned int).
> 
> This issue was observed while doing mkfs.f2fs on 5GB SD card:
> https://lkml.org/lkml/2013/4/1/292
> 
> Info: sector size = 512
> Info: total sectors = 11370496 (in 512bytes)
> Info: zone aligned segment0 blkaddr: 512
> [  257.789764] blk_update_request: bio idx 0 >= vcnt 0
> 
> mkfs process gets stuck in D state and I see the following in the dmesg:
> 
> [  257.789733] __end_that: dev mmcblk0: type=1, flags=122c8081
> [  257.789764]   sector 4194304, nr/cnr 2981888/4294959104
> [  257.789764]   bio df3840c0, biotail df3848c0, buffer   (null), len
> 1526726656
> [  257.789764] blk_update_request: bio idx 0 >= vcnt 0
> [  257.794921] request botched: dev mmcblk0: type=1, flags=122c8081
> [  257.794921]   sector 4194304, nr/cnr 2981888/4294959104
> [  257.794921]   bio df3840c0, biotail df3848c0, buffer   (null), len
> 1526726656
> 
> This patch fixes this issue.
> 
> Reported-by: Max Filippov <jcmvbkbc@gmail.com>
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> Signed-off-by: James Bottomley <JBottomley@Parallels.com>
> Tested-by: Max Filippov <jcmvbkbc@gmail.com>
> Cc: <stable@vger.kernel.org>

Thanks! One minor nit - I don't think James signed off on the patch when
he sent it in. James?

-- 
Jens Axboe


  parent reply	other threads:[~2013-04-24 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 13:55 [PATCH] block: fix max discard sectors limit Namjae Jeon
2013-04-24 14:23 ` James Bottomley
2013-04-24 14:49   ` Jens Axboe
2013-04-24 14:23 ` Jens Axboe [this message]
2013-04-24 14:29   ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2013-04-23 13:06 Namjae Jeon
2013-04-23 13:42 ` James Bottomley
2013-04-23 14:49   ` Max Filippov
2013-04-23 15:54     ` Jens Axboe
2013-04-24  4:09   ` Namjae Jeon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130424142332.GD2759@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=JBottomley@Parallels.com \
    --cc=linkinjeon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.