Skip to contentSkip to conversation

block: don't use for-inside-for in bio_for_each_segment_all

PATCH Superseded Ming Lei 3 participants 5 messages Apr 7, 2019 – Apr 8, 2019

Subsystems (3)

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore

Ming Lei

author
#0 lore raw

PATCH v2 1/1 block: don't use for-inside-for in bio_for_each_segment_all

Commit 6dc4f100c175 ("block: allow bio_for_each_segment_all() to iterate over multi-page bvec") changes bio_for_each_segment_all() to use for-inside-for.

This way breaks all bio_for_each_segment_all() call with error out branch via 'break', since now 'break' can only break from the inner loop.

Fixes this issue by implementing bio_for_each_segment_all() via single 'for' loop, and now the logic is very similar with normal bvec iterator.

Cc Qu Wenruo <[email protected]>
Cc Omar Sandoval <[email protected]>
Cc Christoph Hellwig <[email protected]>
Reported-and-Tested-by Qu Wenruo <[email protected]>
Fixes 6dc4f100c175 ("block: allow bio_for_each_segment_all() to iterate over multi-page bvec")
---
 include/linux/bio.h  | 20 ++++++++++++--------
 include/linux/bvec.h | 23 +++++++++++++++--------
 2 files changed, 27 insertions(+), 16 deletions(-)
include/linux/bio.h +12 -8
index bb6090aa165d..9c583bf98ff9 100644
@@ -120,19 +120,23 @@ static inline bool bio_full(struct bio *bio)
 	return bio->bi_vcnt >= bio->bi_max_vecs;
 }
 
-#define mp_bvec_for_each_segment(bv, bvl, i, iter_all)			\
-	for (bv = bvec_init_iter_all(&iter_all);			\
-		(iter_all.done < (bvl)->bv_len) &&			\
-		(mp_bvec_next_segment((bvl), &iter_all), 1);		\
-		iter_all.done += bv->bv_len, i += 1)
+static inline bool bio_next_segment(const struct bio *bio,
+					 struct bvec_iter_all *iter)
+{
+	if (iter->idx >= bio->bi_vcnt)
+		return false;
+
+	bvec_advance(&bio->bi_io_vec[iter->idx], iter);
+	return true;
+}
 
 /*
  * drivers should _never_ use the all version - the bio may have been split
  * before it got to the driver and the driver won't own all of it
  */
-#define bio_for_each_segment_all(bvl, bio, i, iter_all)		\
-	for (i = 0, iter_all.idx = 0; iter_all.idx < (bio)->bi_vcnt; iter_all.idx++)	\
-		mp_bvec_for_each_segment(bvl, &((bio)->bi_io_vec[iter_all.idx]), i, iter_all)
+#define bio_for_each_segment_all(bvl, bio, i, iter)			\
+	for (i = 0, bvl = bvec_init_iter_all(&iter);			\
+	     bio_next_segment((bio), &iter); i++)
 
 static inline void bio_advance_iter(struct bio *bio, struct bvec_iter *iter,
 				    unsigned bytes)
include/linux/bvec.h +15 -8
index f6275c4da13a..67eda310b643 100644
@@ -47,8 +47,9 @@ struct bvec_iter {
 
 struct bvec_iter_all {
 	struct bio_vec	bv;
-	int		idx;
-	unsigned	done;
+	int		idx;		/* current index into bvec table */
+	unsigned	bvec_done;	/* number of bytes completed in
+					   currnet bvec	*/
 };
 
 static inline struct page *bvec_nth_page(struct page *page, int idx)
@@ -145,18 +146,18 @@ static inline bool bvec_iter_advance(const struct bio_vec *bv,
 
 static inline struct bio_vec *bvec_init_iter_all(struct bvec_iter_all *iter_all)
 {
-	iter_all->bv.bv_page = NULL;
-	iter_all->done = 0;
+	iter_all->bvec_done = 0;
+	iter_all->idx = 0;
 
 	return &iter_all->bv;
 }
 
-static inline void mp_bvec_next_segment(const struct bio_vec *bvec,
-					struct bvec_iter_all *iter_all)
+static inline void bvec_advance(const struct bio_vec *bvec,
+		struct bvec_iter_all *iter_all)
 {
 	struct bio_vec *bv = &iter_all->bv;
 
-	if (bv->bv_page) {
+	if (iter_all->bvec_done) {
 		bv->bv_page = nth_page(bv->bv_page, 1);
 		bv->bv_offset = 0;
 	} else {
@@ -164,7 +165,13 @@ static inline void mp_bvec_next_segment(const struct bio_vec *bvec,
 		bv->bv_offset = bvec->bv_offset;
 	}
 	bv->bv_len = min_t(unsigned int, PAGE_SIZE - bv->bv_offset,
-			   bvec->bv_len - iter_all->done);
+			   bvec->bv_len - iter_all->bvec_done);
+	iter_all->bvec_done += bv->bv_len;
+
+	if (iter_all->bvec_done == bvec->bv_len) {
+		iter_all->idx++;
+		iter_all->bvec_done = 0;
+	}
 }
 
 /*
Signature · 1 line
2.9.5
#2 lore raw
Quoted 3 lines · Christoph Hellwig

Looks good:

Actually.. I just noticed the gratious done rename creates a (trivial) conflict in a series I was about to submit for 5.2. Can you respin it without the rename to make everyones life a littler easier?

#3 lore raw
Quoted 9 lines · Christoph Hellwig
Quoted 3 lines · Christoph Hellwig

Looks good:

Actually.. I just noticed the gratious done rename creates a (trivial) conflict in a series I was about to submit for 5.2. Can you respin it without the rename to make everyones life a littler easier?

Yeah, no problem.

You mean the 'done->bvec_done' rename?

Thanks,
Ming Lei

#4 lore raw
Quoted 7 lines · Ming Lei
Quoted 3 lines

Actually.. I just noticed the gratious done rename creates a (trivial) conflict in a series I was about to submit for 5.2. Can you respin it without the rename to make everyones life a littler easier?

Yeah, no problem.

You mean the 'done->bvec_done' rename?

Yes.