linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Patlasov <maxim.patlasov@gmail.com>
To: psusi@cfl.rr.com
Cc: vgoyal@redhat.com, joe@perches.com, kzak@redhat.com,
	linux-kernel@vger.kernel.org, jaxboe@fusionio.com
Subject: Re: [PATCH 1/2] Add partition resize function to BLKPG ioctl
Date: Thu, 29 Dec 2011 20:06:32 +0300	[thread overview]
Message-ID: <CA+X1aCQRpJ_NwJBSBp+vDN37p+oipJNz=6T5LdJdqzxTiSWWWA@mail.gmail.com> (raw)

Phillip,

The patch seems to have some problems:

1. Typo in part_nr_sects_write_begin:

> +	write_seqcount_begin(&seq);

It should be write_seqcount_begin(seq). Similar issue in
part_nr_sects_write_end().

2. part_nr_sects_write_begin/end is never called.

3. part->seq should be initialized with seqcount_init().

Btw, do we really need both part_nr_sects_write_begin and
part_nr_sects_write_end? What about:

#if BITS_PER_LONG == 32 && defined(CONFIG_LBDAF)
static inline void part_nr_sects_write(struct hd_struct *part,
sector_t nr_sects)
{
        write_seqcount_begin(&part->seq);
        part->nr_sects = nr_sects;
        write_seqcount_end(&part->seq);
}
#else
static inline void part_nr_sects_write(struct hd_struct *part,
sector_t nr_sects)
{
        part->nr_sects = nr_sects;
}
#endif

and use part_nr_sects_write(part, length) instead of part->nr_sects =
length in case BLKPG_RESIZE_PARTITION?

Thanks,
Maxim

             reply	other threads:[~2011-12-29 17:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29 17:06 Maxim Patlasov [this message]
2011-12-30  0:09 ` [PATCH 1/2] Add partition resize function to BLKPG ioctl Phillip Susi
2012-01-01 21:49   ` Phillip Susi
2012-01-26 19:01   ` Vivek Goyal
2012-01-26 20:35     ` Phillip Susi
2012-01-26 21:04       ` Vivek Goyal
2012-01-26 21:48         ` Phillip Susi
2012-01-30 15:49           ` Vivek Goyal
     [not found] <cover.1322709471.git.psusi@cfl.rr.com>
2011-12-01  3:23 ` Phillip Susi
2011-12-08 12:30   ` Karel Zak
2011-12-08 14:22     ` Phillip Susi
2011-12-08 15:16       ` Karel Zak
2011-12-08 15:25         ` Phillip Susi
2011-12-08 15:58           ` Vivek Goyal
2011-12-08 16:06             ` Phillip Susi
2011-12-08 16:28               ` Vivek Goyal
2011-12-08 16:55                 ` Phillip Susi
2011-12-09  2:53                 ` Phillip Susi
2011-12-12 14:53                   ` Vivek Goyal
2011-12-12 17:43                     ` Phillip Susi
2011-12-12 17:49                       ` Joe Perches
2011-12-12 18:04                         ` Vivek Goyal
2011-12-13  0:15                           ` Phillip Susi
2011-12-13  0:16                             ` Phillip Susi
2011-12-19 20:25                               ` Vivek Goyal
2011-12-21  1:53                                 ` Phillip Susi
2011-12-21  1:54                                   ` Phillip Susi
2011-12-21 20:46                                   ` Vivek Goyal
2011-12-24 21:36                                     ` Phillip Susi
2011-12-24 22:21                                       ` Phillip Susi

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='CA+X1aCQRpJ_NwJBSBp+vDN37p+oipJNz=6T5LdJdqzxTiSWWWA@mail.gmail.com' \
    --to=maxim.patlasov@gmail.com \
    --cc=jaxboe@fusionio.com \
    --cc=joe@perches.com \
    --cc=kzak@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psusi@cfl.rr.com \
    --cc=vgoyal@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: 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;
as well as URLs for NNTP newsgroup(s).