[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1358421561.2394.27.camel@dabdike.int.hansenpartnership.com>
Date: Thu, 17 Jan 2013 11:19:21 +0000
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: martin.petersen@...cle.com, linux-scsi@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-mmc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Subhash Jadavani <subhashj@...eaurora.org>,
Tejun Heo <tj@...nel.org>, asias@...hat.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 1/1] block: blk-merge: don't merge the pages with
non-contiguous descriptors
On Thu, 2013-01-17 at 11:04 +0000, Russell King - ARM Linux wrote:
> On Thu, Jan 17, 2013 at 11:01:47AM +0000, James Bottomley wrote:
> > On Thu, 2013-01-17 at 10:47 +0000, Russell King - ARM Linux wrote:
> > > Also, couldn't the addition of the scatterlist offset to the page also
> > > be buggy too?
> >
> > No, fortunately, offset must be within the first page from the point of
> > view of block generated sg lists. As long as nothing within arm
> > violates this, it should be a safe assumption ... although the code
> > seems to assume otherwise.
>
> Are you absolutely sure about that? I believe I have seen cases where
> that has been violated in the past, though it was many years ago.
>From the point of view of the block layer, absolutely: the scatterlist
is generated from an array of bio_vecs. Each bio_vec is a page, offset
and length element and obeys the rule that offset must be within the
page and offset + length cannot stray over the page.
>From the point of view of other arm stuff, I don't know.
James
--
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/
Powered by blists - more mailing lists