From: Andrew Morton <akpm@linux-foundation.org>
To: David Dillow <dillowda@ornl.gov>
Cc: Jeff Moyer <jmoyer@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v3] fs/direct-io.c: don't try to allocate more than BIO_MAX_PAGES in a bio
Date: Tue, 18 Jan 2011 16:53:59 -0800 [thread overview]
Message-ID: <20110118165359.09023fe9.akpm@linux-foundation.org> (raw)
In-Reply-To: <1295319627.3051.89.camel@obelisk.thedillows.org>
On Mon, 17 Jan 2011 22:00:27 -0500
David Dillow <dillowda@ornl.gov> wrote:
> When using devices that support max_segments > BIO_MAX_PAGES (256),
> direct IO tries to allocate a bio with more pages than allowed, which
> leads to an oops in dio_bio_alloc(). Clamp the request to the supported
> maximum, and change dio_bio_alloc() to reflect that bio_alloc() will
> always return a bio when called with __GFP_WAIT and a valid number of
> vectors.
Which device driver triggers this condition?
> Also added cc to stable, as this has been a longstanding item.
Well. -stable only needs the patch if the driver which triggers the
problem is also there. But we don't know what driver that is, yet???
> --- a/fs/direct-io.c
> +++ b/fs/direct-io.c
> @@ -325,13 +325,18 @@ void dio_end_io(struct bio *bio, int error)
> }
> EXPORT_SYMBOL_GPL(dio_end_io);
>
> -static int
> +static void
> dio_bio_alloc(struct dio *dio, struct block_device *bdev,
> sector_t first_sector, int nr_vecs)
> {
> struct bio *bio;
>
> + /*
> + * bio_alloc() is guaranteed to return a bio when called with
> + * __GFP_WAIT and we request a valid number of vectors.
> + */
> bio = bio_alloc(GFP_KERNEL, nr_vecs);
> + BUG_ON(!bio);
This BUG_ON() is pretty pointless,
> bio->bi_bdev = bdev;
because the next statement will reliably oops, providing us with the
same information.
> bio->bi_sector = first_sector;
> @@ -342,7 +347,6 @@ dio_bio_alloc(struct dio *dio, struct block_device *bdev,
>
> dio->bio = bio;
> dio->logical_offset_in_bio = dio->cur_page_fs_offset;
> - return 0;
> }
>
> /*
> @@ -583,8 +587,9 @@ static int dio_new_bio(struct dio *dio, sector_t start_sector)
> goto out;
> sector = start_sector << (dio->blkbits - 9);
> nr_pages = min(dio->pages_in_io, bio_get_nr_vecs(dio->map_bh.b_bdev));
> + nr_pages = min(nr_pages, BIO_MAX_PAGES);
> BUG_ON(nr_pages <= 0);
> - ret = dio_bio_alloc(dio, dio->map_bh.b_bdev, sector, nr_pages);
> + dio_bio_alloc(dio, dio->map_bh.b_bdev, sector, nr_pages);
> dio->boundary = 0;
> out:
> return ret;
>
next prev parent reply other threads:[~2011-01-19 0:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 4:05 fs/direct-io.c: don't try to allocate more than BIO_MAX_PAGES in a bio David Dillow
2011-01-14 14:44 ` Jeff Moyer
2011-01-14 16:46 ` [PATCH v2 alt 1] " David Dillow
2011-01-14 16:46 ` [PATCH v2 alt 2] " David Dillow
2011-01-17 18:28 ` Jeff Moyer
2011-01-18 3:00 ` [PATCH v3] " David Dillow
2011-01-19 0:53 ` Andrew Morton [this message]
2011-01-19 2:34 ` David Dillow
2011-01-19 15:53 ` Boaz Harrosh
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=20110118165359.09023fe9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dillowda@ornl.gov \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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.