All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugene Syromiatnikov <esyr@redhat.com>
To: dm-devel@redhat.com
Cc: agrover@redhat.com, mpatocka@redhat.com
Subject: Re: [PATCH 3/3] dm-ioctl: report event number in DM_LIST_DEVICES
Date: Sun, 17 Sep 2017 04:41:27 +0200	[thread overview]
Message-ID: <20170917023849.GA4094@asgard.redhat.com> (raw)
In-Reply-To: <20170509191028.6898-1-agrover@redhat.com>

> +			event_nr = align_ptr(((void *) (nl + 1)) + strlen(hc->name) + 1);
If my understanding is correct, (nl + 1) differs between 32-bit and
64-bit kernels (as the structure contains of one 8-byte and one 4-byte field),
so this logic is probably broken for compat.

  parent reply	other threads:[~2017-09-17  2:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 19:10 [PATCH 0/3] poll()able DM events Andy Grover
2017-05-09 19:10 ` [PATCH 1/3] dm: a basic support for using the select or poll function Andy Grover
2017-05-11  9:39   ` Martin Wilck
2017-05-11  9:43     ` Martin Wilck
2017-05-11 13:21       ` Mike Snitzer
2017-05-11 18:10         ` Andy Grover
2017-05-11 19:49           ` Martin Wilck
2017-05-11 20:21             ` Alasdair G Kergon
2017-05-11 20:45               ` Martin Wilck
2017-05-11 21:38                 ` Alasdair G Kergon
2017-05-11 19:30         ` Martin Wilck
2017-05-11 21:46           ` Andy Grover
2017-05-12  6:48             ` Martin Wilck
2017-05-11 21:50           ` Alasdair G Kergon
2017-05-12 15:52           ` Mikulas Patocka
2017-05-09 19:10 ` [PATCH 2/3] dm-ioctl: add a new DM_DEV_ARM_POLL ioctl Andy Grover
2017-05-09 19:10 ` [PATCH 3/3] dm-ioctl: report event number in DM_LIST_DEVICES Andy Grover
2017-05-09 21:14 ` [PATCH 0/3] poll()able DM events Mike Snitzer
2017-09-17  2:41 ` Eugene Syromiatnikov [this message]
2017-09-19 16:47   ` [PATCH 3/3] dm-ioctl: report event number in DM_LIST_DEVICES Andy Grover
2017-09-20 11:29   ` [PATCH] dm-ioctl: fix alignment of event number in the device list Mikulas Patocka

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=20170917023849.GA4094@asgard.redhat.com \
    --to=esyr@redhat.com \
    --cc=agrover@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@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 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.