All of lore.kernel.org
 help / color / mirror / Atom feed
From: Blazej Kucman <blazej.kucman@linux.intel.com>
To: Xiao Ni <xni@redhat.com>
Cc: Blazej Kucman <blazej.kucman@intel.com>,
	mariusz.tkaczyk@linux.intel.com, jes@trained-monkey.org,
	linux-raid@vger.kernel.org
Subject: Re: [PATCH v2 2/6] Add reading Opal NVMe encryption information
Date: Thu, 16 May 2024 11:02:46 +0200	[thread overview]
Message-ID: <20240516110246.00003281@linux.intel.com> (raw)
In-Reply-To: <20240515162656.00003dee@linux.intel.com>

On Wed, 15 May 2024 16:26:56 +0200
Blazej Kucman <blazej.kucman@linux.intel.com> wrote:

> On Wed, 15 May 2024 11:20:33 +0800
> Xiao Ni <xni@redhat.com> wrote:
> 
> >
> > Hi all
> > 
> > In i686 platform, it reports error:
> > 
> > drive_encryption.c: In function ‘nvme_security_recv_ioctl’:
> > drive_encryption.c:236:25: error: cast from pointer to integer of
> > different size [-Werror=pointer-to-int-cast]
> >   236 |         nvme_cmd.addr = (__u64)response_buffer;
> >       |                         ^
> > drive_encryption.c: In function ‘nvme_identify_ioctl’:
> > drive_encryption.c:271:25: error: cast from pointer to integer of
> > different size [-Werror=pointer-to-int-cast]
> >   271 |         nvme_cmd.addr = (__u64)response_buffer;
> >       |                         ^
> > cc1: all warnings being treated as errors
> > make: *** [Makefile:211: drive_encryption.o] Error 1
> > 
> > The pointer should be 32bit and it tries to convert to 64 bit.
> > 
> > Best Regards
> > Xiao
> >   
> 
> Hi Xiao,
> Thanks for reporting the issue, I'm already working on a fix,
> I'm currently in the fix testing phase.
> 
> Thanks,
> Blazej
> 

Hi Xiao,
I sent fix to review.
https://github.com/md-raid-utilities/mdadm/pull/9

Regards,
Blazej

  reply	other threads:[~2024-05-16  9:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 11:51 [PATCH v2 0/6] Disk encryption status handling Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 1/6] mdadm: Move pr_vrb define to mdadm.h Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 2/6] Add reading Opal NVMe encryption information Blazej Kucman
2024-05-15  3:20   ` Xiao Ni
2024-05-15 14:26     ` Blazej Kucman
2024-05-16  9:02       ` Blazej Kucman [this message]
2024-03-22 11:51 ` [PATCH v2 3/6] Add reading SATA " Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 4/6] Add key ENCRYPTION_NO_VERIFY to conf Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 5/6] imsm: print disk encryption information Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 6/6] imsm: drive encryption policy implementation Blazej Kucman
2024-04-02  6:32 ` [PATCH v2 0/6] Disk encryption status handling Mariusz Tkaczyk

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=20240516110246.00003281@linux.intel.com \
    --to=blazej.kucman@linux.intel.com \
    --cc=blazej.kucman@intel.com \
    --cc=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mariusz.tkaczyk@linux.intel.com \
    --cc=xni@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.