From: Mike Christie <mchristi@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, ross.zwisler@linux.intel.com,
linux-ext4@vger.kernel.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, david@fromorbit.com,
minchan@kernel.org, ngupta@vflare.org, vishal.l.verma@intel.com
Subject: Re: [PATCH 1/1] mm/block: convert rw_page users to bio op use
Date: Thu, 4 Aug 2016 16:24:40 -0500 [thread overview]
Message-ID: <57A3B298.6040707@redhat.com> (raw)
In-Reply-To: <a49706b7-848f-d558-c253-2b5c4a75a30f@kernel.dk>
On 08/04/2016 03:15 PM, Jens Axboe wrote:
> On 08/04/2016 01:59 PM, Mike Christie wrote:
>> On 08/04/2016 02:27 PM, Jens Axboe wrote:
>>> On 08/04/2016 11:50 AM, kbuild test robot wrote:
>>>> Hi Mike,
>>>>
>>>> [auto build test ERROR on linus/master]
>>>> [also build test ERROR on next-20160804]
>>>> [cannot apply to v4.7]
>>>> [if your patch is applied to the wrong git tree, please drop us a note
>>>> to help improve the system]
>>>>
>>>> url:
>>>> https://github.com/0day-ci/linux/commits/Mike-Christie/mm-block-convert-rw_page-users-to-bio-op-use/20160805-012041
>>>>
>>>>
>>>> config: i386-tinyconfig (attached as .config)
>>>> compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
>>>> reproduce:
>>>> # save the attached .config to linux build tree
>>>> make ARCH=i386
>>>>
>>>> All errors (new ones prefixed by >>):
>>>>
>>>> mm/filemap.c: In function 'page_endio':
>>>>>> mm/filemap.c:892:7: error: implicit declaration of function
>>>>>> 'op_is_write' [-Werror=implicit-function-declaration]
>>>> if (!op_is_write(op)) {
>>>> ^~~~~~~~~~~
>>>
>>> Mike, how about moving op_is_write() outside of CONFIG_BLOCK protection
>>> in fs.h, and making the REQ_OP_* enum generally available as well? That
>>> should fix it.
>>>
>>>
>>> diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
>>> index f254eb264924..14b28ff2caf8 100644
>>> --- a/include/linux/blk_types.h
>>> +++ b/include/linux/blk_types.h
>>> @@ -18,6 +18,17 @@ struct cgroup_subsys_state;
>>> typedef void (bio_end_io_t) (struct bio *);
>>> typedef void (bio_destructor_t) (struct bio *);
>>>
>>> +enum req_op {
>>> + REQ_OP_READ,
>>> + REQ_OP_WRITE,
>>> + REQ_OP_DISCARD, /* request to discard sectors */
>>> + REQ_OP_SECURE_ERASE, /* request to securely erase sectors */
>>> + REQ_OP_WRITE_SAME, /* write same block many times */
>>> + REQ_OP_FLUSH, /* request for cache flush */
>>> +};
>>> +
>>> +#define REQ_OP_BITS 3
>>> +
>>> #ifdef CONFIG_BLOCK
>>> /*
>>> * main unit of I/O for the block layer and lower layers (ie drivers
>>> and
>>> @@ -228,17 +239,6 @@ enum rq_flag_bits {
>>> #define REQ_HASHED (1ULL << __REQ_HASHED)
>>> #define REQ_MQ_INFLIGHT (1ULL << __REQ_MQ_INFLIGHT)
>>>
>>> -enum req_op {
>>> - REQ_OP_READ,
>>> - REQ_OP_WRITE,
>>> - REQ_OP_DISCARD, /* request to discard sectors */
>>> - REQ_OP_SECURE_ERASE, /* request to securely erase sectors */
>>> - REQ_OP_WRITE_SAME, /* write same block many times */
>>> - REQ_OP_FLUSH, /* request for cache flush */
>>> -};
>>> -
>>> -#define REQ_OP_BITS 3
>>> -
>>> typedef unsigned int blk_qc_t;
>>> #define BLK_QC_T_NONE -1U
>>> #define BLK_QC_T_SHIFT 16
>>> diff --git a/include/linux/fs.h b/include/linux/fs.h
>>> index f2a69f20926f..13cc1bfce9aa 100644
>>> --- a/include/linux/fs.h
>>> +++ b/include/linux/fs.h
>>> @@ -2465,12 +2465,13 @@ extern void init_special_inode(struct inode *,
>>> umode_t, dev_t);
>>> extern void make_bad_inode(struct inode *);
>>> extern bool is_bad_inode(struct inode *);
>>>
>>> -#ifdef CONFIG_BLOCK
>>> static inline bool op_is_write(unsigned int op)
>>> {
>>> return op == REQ_OP_READ ? false : true;
>>> }
>>>
>>> +#ifdef CONFIG_BLOCK
>>> +
>>> /*
>>> * return data direction, READ or WRITE
>>> */
>>>
>>
>>
>> Looks ok to me. Did a quick build and test run with it.
>
> Is anyone using the op_flags in the ->rw_page() strategy?
Not in the current code. I had just passed it in because the code was
currently passing that extra info, and I thought the original
implementer was going to use it in the future.
next prev parent reply other threads:[~2016-08-04 21:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 17:17 [PATCH 1/1] mm/block: convert rw_page users to bio op use Mike Christie
2016-08-04 17:50 ` kbuild test robot
2016-08-04 19:27 ` Jens Axboe
2016-08-04 19:59 ` Mike Christie
2016-08-04 20:15 ` Jens Axboe
2016-08-04 21:24 ` Mike Christie [this message]
2016-08-04 21:26 ` Jens Axboe
2016-08-05 2:18 ` Dave Chinner
2016-08-05 3:30 ` Mike Christie
2016-08-05 7:53 ` Christoph Hellwig
2016-08-04 18:46 ` Ross Zwisler
2016-08-04 18:51 ` Mike Christie
2016-08-05 7:57 ` Christoph Hellwig
2016-08-05 13:52 ` Jens Axboe
2016-08-05 14:09 ` Jens Axboe
2016-08-05 18:05 ` Mike Christie
2016-08-05 21:27 ` Jens Axboe
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=57A3B298.6040707@redhat.com \
--to=mchristi@redhat.com \
--cc=axboe@kernel.dk \
--cc=david@fromorbit.com \
--cc=kbuild-all@01.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=ross.zwisler@linux.intel.com \
--cc=vishal.l.verma@intel.com \
/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.