$ ./change-override -c main -t ndctl
Override component to main
ndctl 67-1 in focal: universe/libs -> main
Override [y|N]? y
1 publication overridden.
$ ./change-override -c main libdaxctl-dev libdaxctl1 libndctl-dev libndctl6
ndctl
Override component to main
libdaxctl-dev 67-1 in focal amd64:
Andreas' merge proposal for adding tests to q-r-t has been merged in to
master. Thanks Andreas!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853506
Title:
[MIR] ndctl
To manage notifications
MP for the first batch of tests to be added to q-r-t:
https://code.launchpad.net/~ahasenack/qa-regression-testing/+git/qa-
regression-testing/+merge/378543
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/qa-regression-testing/+git/qa-regression-testing/+merge/378543
--
You
MP for the first batch of tests to be added to q-r-t:
https://code.launchpad.net/~ahasenack/qa-regression-testing/+git/qa-
regression-testing/+merge/378543
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/qa-regression-testing/+git/qa-regression-testing/+merge/378543
--
You
Quick update on progress. Of all these tests that were written:
blk-exhaust
btt-check
btt-pad-compat
dax
dax-ext4
dax-xfs
daxctl-commands
label-compat
multi-dax
ndctl-commands
rescan-partitions
sector-mode
Only multi-dax and sector-mode are failing on bionic, and rescan-
partitions is being
Quick update on progress. Of all these tests that were written:
blk-exhaust
btt-check
btt-pad-compat
dax
dax-ext4
dax-xfs
daxctl-commands
label-compat
multi-dax
ndctl-commands
rescan-partitions
sector-mode
Only multi-dax and sector-mode are failing on bionic, and rescan-
partitions is being
\o/ glad you found this!
@andreas:
While I was at PMDK adding one more was easy, MP suggestion for the seed
change:
https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/platform/+merge/378436
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Oh thats nice to hear that... I was getting worried (coming back from
vacation and reading backlog). Thanks Andreas for testing this and Dan
for the help.
On Fri, Jan 31, 2020 at 10:41 PM Andreas Hasenack wrote:
>
> hah, bingo, the default kernel package for VMs doesn't have nd_pmem or
> nd_btt.
Oh thats nice to hear that... I was getting worried (coming back from
vacation and reading backlog). Thanks Andreas for testing this and Dan
for the help.
On Fri, Jan 31, 2020 at 10:41 PM Andreas Hasenack wrote:
>
> hah, bingo, the default kernel package for VMs doesn't have nd_pmem or
> nd_btt.
@djbw do you mean a kernel module?
Here is the full dmesg. I just logged in and ran "sudo ndctl create-
namespace":
https://paste.ubuntu.com/p/Mf2g282JNQ/
lsmod: https://paste.ubuntu.com/p/GqTvskG7RJ/
/proc/iomem (it shows some lines with "Persistent Memory"):
hah, bingo, the default kernel package for VMs doesn't have nd_pmem or
nd_btt. I had to install linux-modules-extra-5.4.0-12-generic.
Now it works:
ubuntu@focal-nvdimm:~$ sudo ndctl create-namespace
{
"dev":"namespace1.0",
"mode":"fsdax",
"map":"dev",
"size":"1006.00 MiB (1054.87 MB)",
hah, bingo, the default kernel package for VMs doesn't have nd_pmem or
nd_btt. I had to install linux-modules-extra-5.4.0-12-generic.
Now it works:
ubuntu@focal-nvdimm:~$ sudo ndctl create-namespace
{
"dev":"namespace1.0",
"mode":"fsdax",
"map":"dev",
"size":"1006.00 MiB (1054.87 MB)",
@djbw do you mean a kernel module?
Here is the full dmesg. I just logged in and ran "sudo ndctl create-
namespace":
https://paste.ubuntu.com/p/Mf2g282JNQ/
lsmod: https://paste.ubuntu.com/p/GqTvskG7RJ/
/proc/iomem (it shows some lines with "Persistent Memory"):
@andreas this almost looks like the pmem module is missing. Can you
paste the full dmesg on pastebin and verify that the driver is present?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853506
I get nothing in dmesg when I run enable-namespace all:
root@focal-nvdimm:~# ndctl enable-namespace all
libndctl: ndctl_namespace_enable: namespace1.0: failed to enable
libndctl: ndctl_namespace_enable: namespace0.0: failed to enable
error enabling namespaces: No such device or address
enabled 0
I get nothing in dmesg when I run enable-namespace all:
root@focal-nvdimm:~# ndctl enable-namespace all
libndctl: ndctl_namespace_enable: namespace1.0: failed to enable
libndctl: ndctl_namespace_enable: namespace0.0: failed to enable
error enabling namespaces: No such device or address
enabled 0
@andreas - you'll have a pmem enabled qemu in PPA: https://launchpad.net
/~ci-train-ppa-service/+archive/ubuntu/3883
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853506
Title:
[MIR] ndctl
To
@andreas, can you paste a full dmesg after turning on driver debug and
retrying the create-namespace? Either boot with:
libnvdimm.dyndbg=+fp
...on the kernel command line or:
echo "module libnvdimm +fp" >
/sys/kernel/debug/dynamic_debug/control
--
You received this bug notification
I also tried rebuilding qemu with pmem support, but qemu is currently an
FTBFS in focal (https://launchpad.net/ubuntu/+source/qemu/1:4.0+dfsg-
0ubuntu11)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
I also tried rebuilding qemu with pmem support, but qemu is currently an
FTBFS in focal (https://launchpad.net/ubuntu/+source/qemu/1:4.0+dfsg-
0ubuntu11)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is the libvirt vm definition:
https://pastebin.ubuntu.com/p/tjzwHbJMpT/
Here are some commands I tried and their results:
https://pastebin.ubuntu.com/p/3Sn74Kp8KH/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm having a hard time in getting a VM up and running with the correct
support for the ndctl commands, and I'm not sure what is going on.
@paelzer also tried, and got the same error. Basically any enable-
namespace or create-namespace command fails complaining about "no such
device".
I also tried
This is the libvirt vm definition:
https://pastebin.ubuntu.com/p/tjzwHbJMpT/
Here are some commands I tried and their results:
https://pastebin.ubuntu.com/p/3Sn74Kp8KH/
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
I'm having a hard time in getting a VM up and running with the correct
support for the ndctl commands, and I'm not sure what is going on.
@paelzer also tried, and got the same error. Basically any enable-
namespace or create-namespace command fails complaining about "no such
device".
I also tried
bug 1853506 and bug 1790856 are ready (process-wise) when you are @ahasenack.
As checked on IRC, let me know when all is ready to add the dependency pulling
it in.
** Changed in: ndctl (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: ndctl (Ubuntu)
I reviewed ndctl as checked into focal. This shouldn't be considered a
full audit but rather a quick gauge of maintainability.
ndctl is comprised of utilities and libraries for managing the libnvdimm
(non-volatile memory device) sub-system in the Linux kernel
- No CVEs readily found.
Gleaned
** Changed in: ndctl (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853506
Title:
[MIR] ndctl
To manage notifications
BUG (MIR): https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1853506
MERGE:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/ndctl/+git/ndctl/+merge/376493
** Merge proposal linked:
I have changed the merge request as it had the wrong LP # on it (just
realized that). I have included Adam's suggestions and will, in a near
future, differentiate tests working with kernel cmdline from these
working in a virtual environment (both outside the automated bileto
scope).
Waiting for
I'm changing it to:
ubuntu: convert ndctl/test into qa-regression-ndctl tests
Adding regression tests based in existing upstream tests. While upstream
is worried about testing the entire pmem/dax stack (including kernel
libnvdimm using a mocked driver) our need is much
Yes Adam, my commit should have mentioned that! Maybe even referenced
"https://docs.pmem.io/getting-started-guide/creating-development-
environments/linux-environments/linux-memmap" or some other doc about
it.
Thanks for pointing that out!
I'll rephrase that, so others willing to do autopkgtest
Unlike what your commit message says, you _can_ run at least some of the
functionality with no HW and no specially configured qemu: append
memmap=4G!20G to the kernel's cmdline, where "4G" is the size of an
emulated nvdimm, and 20G is its start in physical memory. This stanza
can be used multiple
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/ndctl/+git/ndctl/+merge/376487
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853506
Title:
[MIR] ndctl
To
A merge proposal for all the tests I adapted:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/ndctl/+git/ndctl/+merge/376487
This makes much easier to run and support those tests (specially with a
xml example file provided on how to create the autopkgtest environment).
** Attachment
** Attachment removed:
"canonical-convert-ndctl-test-into-qa-regression-ndctl.patch"
https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506/+attachment/5310106/+files/canonical-convert-ndctl-test-into-qa-regression-ndctl.patch
** Patch added:
A few comments on the test (explained in the git commit log):
[PATCH] canonical: convert ndctl/test into qa-regression-ndctl tests
## good tests (bad results mean something)
blk-exhaust.sh
btt-check.sh
btt-pad-compat.sh
label-compat.sh
multi-dax.sh
This patch, applied to ndctl code upstream (v67-1-gf6cafcf), or focal
devel, creates the testing environment we need. I have also created
another set of scripts to create the virtual environment for the nvdimms
emulation which I'll inform soon.
TL;DR is:
- a set of scripts will provision a
Yes Seth!
Unfortunately (or not, as picking up things like this in this phase is
very good) there is an on-going issue with nvdimm regions boundaries.
I'm documenting everything in another bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855177
And the issue is well known upstream
On Wed, Dec 04, 2019 at 08:44:44PM -, Rafael David Tinoco wrote:
> sorry for the delay here, I've been working in making a qa-regression
> test available for the security team, and will push into your
> repository, but I had to struggle with things like:
>
>
hello Seth,
sorry for the delay here, I've been working in making a qa-regression
test available for the security team, and will push into your
repository, but I had to struggle with things like:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855177
and so. I believe I'm almost finishing
Dep-8 tests for what can be tested there, and qrt tests for what can't /
shouldn't be tested there sound wonderful and go a very long way towards
alleviating my concerns.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 26/11/2019 04:01, Christian Ehrhardt wrote:
> @Rafael - Seths comment is correct but I think can be alleviated with
> instructions how to do that on virtual HW. I know you have testing info on
> bug 1811785 and that you are working on more aspects of it, so maybe you have
> even
@Rafael - Seths comment is correct but I think can be alleviated with
instructions how to do that on virtual HW. I know you have testing info on bug
1811785 and that you are working on more aspects of it, so maybe you have even
better/extended instructions now.
I'd ask you to)
a) add a comment
My first and most pressing concern is hardware availability: certainly
none of us on the security team have nvdimm hardware at the moment and
getting systems for this is probably beyond the usual hardware refresh
budget.
At a minimum we'll need someone else's commitment to test updates as
[Summary]
- looks up to date and well packaged
- MIR Team ack (constraint to add the subscription before promotion)
- Needs security review
- subscribing and assigning to security now
- some minimal optional improvements that should be looked at briefly at least
- over-linking warnings by
** Changed in: ndctl (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853506
Title:
[MIR] ndctl
To manage notifications about
** Description changed:
https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506
[Availability]
There is an on-going MIR for a package whose ndctl is a dependency:
pmdk (LP: #1790856)
* Package exists since bionic (-updates) in universe:
61.2-0ubuntu1~18.04.1 |
When using dax:
(k)rafaeldtinoco@emulated:~$ sudo mount -o dax /dev/pmem0p1 /mnt
(k)rafaeldtinoco@emulated:~$ mount | grep -i mnt
/dev/pmem0p1 on /mnt type ext4 (rw,relatime,dax,stripe=512)
(k)rafaeldtinoco@emulated:~$ dd if=/dev/zero of=./teste bs=1M count=1024
1024+0 records in
1024+0 records
This is a good XML template for a VM emulating nvdimms.
** Attachment added: "emulated_vm.xml"
https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506/+attachment/5307204/+files/emulated_vm.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(k)rafaeldtinoco@emulated:~$ sudo ndctl enable-dimm all
enabled 2 nmems
(k)rafaeldtinoco@emulated:~$ sudo ndctl list -D
[
{
"dev":"nmem1",
"id":"8680-57341200",
"handle":2,
"phys_id":0,
"flag_failed_arm":true
},
{
"dev":"nmem0",
"id":"8680-56341200",
50 matches
Mail list logo
