小伙伴们还记得支付宝去年的超大消费红包么？
少的有几块，多的有几百。
后来因为薅羊毛的人太多，市场影响也不是太好，支付宝关闭了这个活动。
可是，就在这两天支付宝红包又火了！
和去年相比，它偷偷换了种玩法，但红包还是同样给力，少的有几块多的有几十。
目前就我知道的，最高有领到上百的。
领取红包的方式很简单，每天直接在支付宝首页搜索“ 7807299 ”就可以领取了。
（一定要记得红包领取号码： 7807299 （每天都可以领哦））
使用余额宝红包： 必须先开通余额宝并且余额宝要有钱！（存几分都行）
进入领取界面后，有两个红包可以领。
On Tue 10-07-18 13:10:29, Ross Zwisler wrote:
> Changes since v3:
> * Added an ext4_break_layouts() call to ext4_insert_range() to ensure
>that the {ext4,xfs}_break_layouts() calls have the same meaning.
>(Dave, Darrick and Jan)
How about the occasional WARN_ON_ONCE you mention below.
Hello Dave Jiang,
This is a semi-automatic email about new static checker warnings.
The patch c1985cefd844: "acpi/nfit: fix cmd_rc for acpi_nfit_ctl to
always return a value" from Jun 28, 2018, leads to the following
Smatch complaint:
drivers/acpi/nfit/core.c:578 acpi_nfit_ctl()
Incremental patch to fix the unchecked dereference in acpi_nfit_ctl.
Reported by Dan Carpenter:
"acpi/nfit: fix cmd_rc for acpi_nfit_ctl to
always return a value" from Jun 28, 2018, leads to the following
Smatch complaint:
drivers/acpi/nfit/core.c:578 acpi_nfit_ctl()
warn: variable
On Wed, Jul 11, 2018 at 10:10 AM, Dave Jiang wrote:
> Incremental patch to fix the unchecked dereference in acpi_nfit_ctl.
> Reported by Dan Carpenter:
>
> "acpi/nfit: fix cmd_rc for acpi_nfit_ctl to
> always return a value" from Jun 28, 2018, leads to the following
> Smatch complaint:
>
>
On 07/06, Dan Williams wrote:
> On Fri, Jul 6, 2018 at 1:32 PM, Verma, Vishal L
> wrote:
> >
[..]
> > Yes, but that gets overriden by:
> > https://github.com/pmem/ndctl/blob/master/test/dax.sh#L33
>
> Hmm not sure. I instrumented dax-pmd.c and the shell script to dump
> the rc value:
>
>
On Wed, Jul 11, 2018 at 10:17:41AM +0200, Jan Kara wrote:
> On Tue 10-07-18 13:10:29, Ross Zwisler wrote:
> > Changes since v3:
> > * Added an ext4_break_layouts() call to ext4_insert_range() to ensure
> >that the {ext4,xfs}_break_layouts() calls have the same meaning.
> >(Dave, Darrick
cmd_rc is passed in by reference to the acpi_nfit_ctl() function and the
caller expects a value returned. However, when the package is pass through
via the ND_CMD_CALL command, cmd_rc is not touched. Make sure cmd_rc is
always set.
Fixes: aef253382266 ("libnvdimm, nfit: centralize command status
The ndctl inject-smart doesn't have a [-H | --health] option.
This patch replaces [-H | --health] in the manpage of inject-smart
with [-f | --fatal].
Signed-off-by: QI Fuli
---
Documentation/ndctl/ndctl-inject-smart.txt | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff
A sub-set of the unit tests are optionally included in the build when
"--enable-test" is specified to the configure script. However, the "ndctl
test" command support code should not be included in the build when
"--enable-test" is not specified. The linker was being helpful and
throwing away the
On Wed, Jul 11, 2018 at 1:28 PM, Vishal Verma wrote:
>
> The device-dax test used heuristic timeouts for distinction between
> cached and uncached accesses. The timeout was too short for emulated
> e820 on a virtual machine. Increased the cached timeout to ~30ms, which
> still keeps it
The original test/common conversions missed the --enable-destructive
class of tests. The json single object vs. array changes prompted
changes to the json2var definitions, which these tests had a local copy
of. Instead of fixing up these local copies, take the change to properly
convert these
The commit below updated json listings to always be arrays unless,
potentially, --human was specified. As a fallout of the change, some
unit tests that used jq to look for certain elements, or the json2var
conversion broke in certain cases. Fix the jq query in sector-mode.sh,
and fix json2var in
The device-dax test used heuristic timeouts for distinction between
cached and uncached accesses. The timeout was too short for emulated
e820 on a virtual machine. Increased the cached timeout to ~30ms, which
still keeps it significantly far from the cached time of 200ms.
Cc: Dan Williams
On Wed, 2018-07-11 at 14:38 -0700, Dan Williams wrote:
> On Wed, Jul 11, 2018 at 2:17 PM, Vishal Verma
> wrote:
> > Add an API to check whether smart injection is supported, and add an
> > intel-dsm implementation for it. Use this check in the ndctl
> > inject-smart command.
> >
> >
On Wed, Jul 11, 2018 at 2:17 PM, Vishal Verma wrote:
> Add an API to check whether smart injection is supported, and add an
> intel-dsm implementation for it. Use this check in the ndctl
> inject-smart command.
>
> Reported-by: Leszek Lugin
> Cc: Dan Williams
> Signed-off-by: Vishal Verma
[..]
linux-nvdimm：亲，您好
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
On Wed, 2018-07-11 at 21:51 +, Verma, Vishal L wrote:
> On Wed, 2018-07-11 at 14:38 -0700, Dan Williams wrote:
> > On Wed, Jul 11, 2018 at 2:17 PM, Vishal Verma > .com> wrote:
> > > Add an API to check whether smart injection is supported, and add an
> > > intel-dsm implementation for it.
Add an API to check whether smart injection is supported, and add an
intel-dsm implementation for it. Use this check in the ndctl
inject-smart command.
Reported-by: Leszek Lugin
Cc: Dan Williams
Signed-off-by: Vishal Verma
---
ndctl/inject-smart.c | 16
ndctl/lib/intel.c
Add support for setting and/or updating passphrase on the Intel nvdimms.
The passphrase is pulled from userspace through the kernel key management.
We trigger the update via writing "update" to the sysfs attribute
"security". The state of the security can also be read via the "security"
attribute.
Add support to allow query the security status of the Intel nvdimms and
also unlock the dimm via the kernel key management APIs. The passphrase is
expected to be pulled from userspace through keyutils. Moving the Intel
related bits to its own source file as well.
Signed-off-by: Dave Jiang
---
Add theory of operation for the security support that's going into
libnvdimm.
Signed-off-by: Dave Jiang
---
Documentation/nvdimm/security | 70 +
1 file changed, 70 insertions(+)
create mode 100644 Documentation/nvdimm/security
diff --git
Add support for freeze security on Intel nvdimm. This locks out any
changes to security for the DIMM unless a reboot is done. This is triggered
by writing "freeze" to the "security" sysfs attribute. libnvdimm will
support the generic freeze_lock API call.
Signed-off-by: Dave Jiang
---
Add nfit_test support for DSM functions "Get Security State",
"Set Passphrase", "Disable Passphrase", "Unlock Unit", "Freeze Lock",
and "Secure Erase" for the fake DIMMs.
Also adding a sysfs knob in order to put the DIMMs in "locked" state. The
order of testing DIMM unlocking would be.
1a. Set
Add support to issue a secure erase DSM to the Intel nvdimm. The
required passphrase is acquired from userspace through the kernel key
management. To trigger the action, "erase" is written to the "security"
sysfs attribute. libnvdimm will support the erase generic API call.
Signed-off-by: Dave
The generated dimm id is needed for the sysfs attribute as well as being
used as the identifier/description for the security key. Since it's
constant and should never change, store it as a member of struct nvdimm.
Signed-off-by: Dave Jiang
---
drivers/acpi/nfit/core.c | 35
In order to access the nfit_test context via sideband sysfs knobs, the
dimm_dev needs to be more than struct device in order to point back to
struct nfit_test. Wrapping the original struct device with a struct
nfit_dimm_dev and saving the nfit_test as private driver data. Also
changing the
Add command definition for security commands defined in Intel DSM
specification v1.7. This includes "get security state", "set passphrase",
"unlock unit", "freeze lock", "secure erase", "ovewrite", and
"overwrite query". Since we are adding a lot of Intel definitions, moving
the relevant bits to
Add support to disable passphrase (security) for the Intel nvdimm. The
passphrase used for disabling is pulled from userspace via the kernel
key management. The action is triggered by writing "disable" to the sysfs
attribute "security". libnvdimm will support the generic disable API call.
On Tue, 2018-06-26 at 12:26 -0600, Keith Busch wrote:
> The available_size attribute returns all the unused regions, but a
> namespace has to use contiguous free regions. This patch uses the
> attribute returning the largest capacity that can be created for
> determining if the namespace can be
A sub-set of the unit tests are optionally included in the build when
"--enable-test" is specified to the configure script. However, the "ndctl
test" command support code should not be included in the build when
"--enable-test" is not specified. The linker was being helpful and
throwing away the
Add an API to check whether smart injection is supported, and add an
intel-dsm implementation for it. Use this check in the ndctl
inject-smart command.
Reported-by: Leszek Lugin
Cc: Dan Williams
Signed-off-by: Vishal Verma
---
ndctl/inject-smart.c | 16
ndctl/lib/intel.c
Prepping the libnvdimm to support security management by adding a keyring
in order to provide passphrase management through the kernel key management
APIs.
Signed-off-by: Dave Jiang
---
drivers/nvdimm/core.c |7 +++
drivers/nvdimm/dimm_devs.c | 96
The following series implements security support for nvdimm. Mostly adding
new security DSM support from the Intel NVDIMM DSM spec v1.7, but also
adding generic support libnvdimm for other vendors. The most important
security features are unlocking locked nvdimms, and updating/setting security
Use the mock config to determine the release to build for, as that will
result in a build version for the running system. If the build were to
fail, ensure we catch that, and if the build artifacts are missing,
error out on that.
Signed-off-by: Vishal Verma
---
contrib/do_abidiff | 6 +-
1
35 matches
Mail list logo
