The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	Min Li <min15.li@samsung.com>,
	axboe@kernel.dk, willy@infradead.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] block: add check that partition length needs to be aligned with block size
Date: Tue, 27 Jun 2023 08:18:32 +0200	[thread overview]
Message-ID: <2023062753-speech-straw-f2f6@gregkh> (raw)
In-Reply-To: <20230627045924.GA16913@lst.de>

On Tue, Jun 27, 2023 at 06:59:24AM +0200, Christoph Hellwig wrote:
> On Tue, Jun 27, 2023 at 01:39:26PM +0900, Damien Le Moal wrote:
> > See Greg's comment: this likely need a "Fixes:" tag. And I think that the tag
> > is: fa9156ae597c ("block: refactor blkpg_ioctl"). But please double check.
> 
> No, the lack of checks goes back all the way to when this code was
> added long before git was a thing.  So I don't think a Fixes tag makes
> all that much sense here.

Ok, then how about a normal "cc: stable@kernel.org" added to the s-o-b
area so it gets picked up for all stable trees as this is an issue that
has always been there?

thanks,

greg k-h

  reply	other threads:[~2023-06-27  6:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230627031105epcas5p3010432ebd447ad865c3ddd986b3ffee0@epcas5p3.samsung.com>
2023-06-27 11:09 ` [PATCH v2] block: add check that partition length needs to be aligned with block size Min Li
2023-06-27  4:19   ` Chaitanya Kulkarni
2023-06-27  4:39   ` Damien Le Moal
2023-06-27  4:59     ` Christoph Hellwig
2023-06-27  6:18       ` Greg KH [this message]
2023-06-27  6:21         ` Christoph Hellwig
2023-06-27  8:13     ` Pankaj Raghav
2023-06-27 17:53       ` Matthew Wilcox
2023-06-27  4:59   ` Christoph Hellwig

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=2023062753-speech-straw-f2f6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=min15.li@samsung.com \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox