From: Bart Van Assche <bart.vanassche@sandisk.com> To: Jens Axboe <axboe@fb.com> Cc: Mike Christie <mchristi@redhat.com>, Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>, Mike Snitzer <snitzer@redhat.com>, Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>, Damien Le Moal <damien.lemoal@hgst.com>, "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>, <linux-btrfs@vger.kernel.org>, "device-mapper development" <dm-devel@redhat.com> Subject: [PATCH 0/3] block: Improve bio_set_op_attrs() robustness Date: Wed, 14 Sep 2016 10:42:37 +0200 [thread overview] Message-ID: <35e3cdd6-8983-6c84-cb4c-9a7be15aea55@sandisk.com> (raw) Hi Jens, bio_set_op_attrs() does not yet check whether the "op_flags" field overflows into the "op" field. Since adding support for SMR requires to introduce more REQ_* flags I think it is important to have such a check. Hence this patch series. Please consider these patches for inclusion in the upstream Linux kernel. Thanks, Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bart.vanassche@sandisk.com> To: Jens Axboe <axboe@fb.com> Cc: Mike Christie <mchristi@redhat.com>, Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>, Mike Snitzer <snitzer@redhat.com>, Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>, Damien Le Moal <damien.lemoal@hgst.com>, "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>, linux-btrfs@vger.kernel.org, device-mapper development <dm-devel@redhat.com> Subject: [PATCH 0/3] block: Improve bio_set_op_attrs() robustness Date: Wed, 14 Sep 2016 10:42:37 +0200 [thread overview] Message-ID: <35e3cdd6-8983-6c84-cb4c-9a7be15aea55@sandisk.com> (raw) Hi Jens, bio_set_op_attrs() does not yet check whether the "op_flags" field overflows into the "op" field. Since adding support for SMR requires to introduce more REQ_* flags I think it is important to have such a check. Hence this patch series. Please consider these patches for inclusion in the upstream Linux kernel. Thanks, Bart.
next reply other threads:[~2016-09-14 8:42 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-09-14 8:42 Bart Van Assche [this message] 2016-09-14 8:42 ` [PATCH 0/3] block: Improve bio_set_op_attrs() robustness Bart Van Assche 2016-09-14 8:44 ` [PATCH 1/3] block: Document that bio_op() uses the data type of bio.bi_opf Bart Van Assche 2016-09-14 8:52 ` Johannes Thumshirn 2016-09-14 8:52 ` Johannes Thumshirn 2016-09-14 9:56 ` Christoph Hellwig 2016-09-14 8:45 ` [PATCH 2/3] block, dm-crypt, btrfs: Introduce bio_flags() Bart Van Assche 2016-09-14 8:53 ` Johannes Thumshirn 2016-09-14 8:53 ` Johannes Thumshirn 2016-09-14 9:58 ` Christoph Hellwig 2016-09-14 9:59 ` Christoph Hellwig 2016-09-14 8:46 ` [PATCH 3/3] block: Improve bio_set_op_attrs() robustness Bart Van Assche 2016-09-14 8:55 ` Johannes Thumshirn 2016-09-14 8:55 ` Johannes Thumshirn 2016-09-14 9:59 ` Christoph Hellwig 2016-09-14 14:48 ` [PATCH 0/3] " Jens Axboe 2016-09-14 14:48 ` 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=35e3cdd6-8983-6c84-cb4c-9a7be15aea55@sandisk.com \ --to=bart.vanassche@sandisk.com \ --cc=axboe@fb.com \ --cc=clm@fb.com \ --cc=damien.lemoal@hgst.com \ --cc=dm-devel@redhat.com \ --cc=hare@suse.de \ --cc=hch@lst.de \ --cc=jbacik@fb.com \ --cc=linux-block@vger.kernel.org \ --cc=linux-btrfs@vger.kernel.org \ --cc=mchristi@redhat.com \ --cc=snitzer@redhat.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: linkBe 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.