search for: gadget

...;'re doing here, or is it a problem with ActiveRecord? We''re on rails 1.1.6 at the moment, so if this is a known bug that''s fixed in 1.2, just club me over the head with the trac reference. Given the following two models.... -------------------------------------------- class Gadget < ActiveRecord::Base has_one :widget end class Widget < ActiveRecord::Base belongs_to :gadget def save gadget.save super end end ------------------------------------------- and the following test.... ------------------------------------------- class WidgetTest < Test::Unit...

Given the following.. Foo has_many :bars Bar has_many ::widgets Widget has_many :gadgets Gadget has_many :parts All of the following are now possible... @foo.bars @bar.widgets @part.gadget.widget.bar.foo However, I can''t just do the opposite of that last one... @foo.bars.widgets.gadgets.parts and get a full list of every Part associated with @foo. I know there''...

Greetings Everyone, I have created a new Google Gadget, this gadget combines three awesome services by Google, Gadget, Ajax Web Search and Custom Search Engine. All glued together with very well designed javascript classes built with prototypejs. The gadget is flexible in its settings to allow any CSE or site restriction but with a few customization...

On Fri, Aug 7, 2020 at 1:18 AM David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > I think it would be useful for the discussion to have a clear threat model that this intends to defend against and a rough analysis of the security benefits that this is believed to bring. I view this as being even more about a ROP defense. Dealing with spill slots is, IMO, a separate issue, more

...; > > > https://gcc.gnu.org/pipermail/gcc-patches/2020-August/551607.html > > This link gives two motivations: > > 1. Reducing information leak (which I find unconvincing, because there's > a lot more left on the stack than in caller-save registers). > 2. Reducing ROP gadgets. > > Unfortunately, for claim 2 they cite a paper that is behind a paywall, > so I can't easily see what that's doing and I'll have to guess what the > paper says: > > Caller-save registers are intuitively useful in the first gadget in a > ROP sequence, because the...

I have two UPSs, one is not connected to a computer. I am looking for a gadget that I can plug in to the other one so I can see the time remaining without a computer.

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API.

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API.

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API. Changes since v1: - drop a few patches - fix a comment typo - cover the newly merged use_mm/unuse_mm caller in vfio

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API. Changes since v1: - drop a few patches - fix a comment typo - cover the newly merged use_mm/unuse_mm caller in vfio

...or has ->mm set in the case of unuse_mm). Also give the functions a kthread_ prefix to better document the use case. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h | 4 +-- drivers/gpu/drm/i915/gvt/kvmgt.c | 4 +-- drivers/usb/gadget/function/f_fs.c | 4 +-- drivers/usb/gadget/legacy/inode.c | 4 +-- drivers/vhost/vhost.c | 4 +-- fs/io-wq.c | 6 ++-- fs/io_uring.c | 6 ++-- include/linux/kthread.h | 4 +--...

...functions a kthread_ prefix to better document the use case. Signed-off-by: Christoph Hellwig <hch at lst.de> Acked-by: Felix Kuehling <Felix.Kuehling at amd.com> --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h | 4 +-- drivers/gpu/drm/i915/gvt/kvmgt.c | 4 +-- drivers/usb/gadget/function/f_fs.c | 4 +-- drivers/usb/gadget/legacy/inode.c | 4 +-- drivers/vfio/vfio_iommu_type1.c | 4 +-- drivers/vhost/vhost.c | 4 +-- fs/io-wq.c | 6 ++-- fs/io_uring.c | 6 ++--...

> On Nov 21, 2019, at 14:23, Robinson, Paul via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Some years ago there was a random-nop-insertion pass (for ROP gadget removal) proposed, which didn't stick; we recently had a summer intern work on it but did not get to proper quality; I'd like to revive that. Hi Paul, I'm curious about what the use case for this was. In the normal course of binary distribution of programs, the addition of nops doesn&...

...red Server distro (Being RHCE certified I am more comfortable in an RPM enivronment) I am wanting to help spread the word of CentOS, but also help within the existing CentOS community. One idea I had, which I discussed with Karan briefly on Twitter a few weeks ago was building a number of iGoogle gadgets for various RSS feeds on centos.org (EG planet.centos.org and the main category forums) but I wish to appeal to the wider community for other CentOS related RSS feeds we could look at gadgetising. I am not necessarily meaning someone who has a few centos articles on their blog - but I am meaning...

...urus.c | 1 - .../drm/amd/amdgpu/amdgpu_amdkfd_gfx_v10.c | 1 - .../gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v7.c | 2 - .../gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.c | 2 - .../gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c | 2 - drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- drivers/usb/gadget/function/f_fs.c | 2 +- drivers/usb/gadget/legacy/inode.c | 2 +- drivers/vhost/vhost.c | 1 - fs/aio.c | 1 - fs/io-wq.c | 1 - fs/io_uring.c...

...uot;clever" optimizations for what usually is just a trivial asignment to a member in the thread_struct for most architectures. Make kthread_use_mm set USER_DS, and kthread_unuse_mm restore to the previous value instead. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/usb/gadget/function/f_fs.c | 4 ---- drivers/vhost/vhost.c | 3 --- fs/io-wq.c | 8 ++------ fs/io_uring.c | 4 ---- kernel/kthread.c | 6 ++++++ 5 files changed, 8 insertions(+), 17 deletions(-) diff --git a/drivers/usb/gadget/funct...

...al asignment to a member in the thread_struct for most architectures. Make kthread_use_mm set USER_DS, and kthread_unuse_mm restore to the previous value instead. Signed-off-by: Christoph Hellwig <hch at lst.de> Acked-by: Michael S. Tsirkin <mst at redhat.com> [vhost] --- drivers/usb/gadget/function/f_fs.c | 4 ---- drivers/vhost/vhost.c | 3 --- fs/io-wq.c | 8 ++------ fs/io_uring.c | 4 ---- kernel/kthread.c | 6 ++++++ 5 files changed, 8 insertions(+), 17 deletions(-) diff --git a/drivers/usb/gadget/funct...

Hi, Sean Silva via llvm-dev wrote: > Wouldn't a branch funnel open the door to a type 1 attack? Only if the code looks exactly as you wrote it. If I understand this correctly the problem with indirect branches is that the "gadget", the code leaking the data, could be *anywhere* in the binary, giving the attacker much more freedom. So restricting these calls to one of the known correct results will still be a (relative) win. Hand-Wavy Example: struct Base { virtual int f(long) = 0; }; struct A : Base {...

See: https://arstechnica.com/gadgets/2021/01/centos-is-gone-but-rhel-is-now-free-for-up-to-16-production-servers/ and https://www.redhat.com/en/blog/new-year-new-red-hat-enterprise-linux-programs-easier-ways-access-rhel -- J Martin Rushton MBCS

...ay speculatively execute the instructions immediately following what should be a change in control flow, including RET (returns), BR (indirect jumps) and BLR (indirect function calls). If the speculative execution path contains a suitable code sequence, often described as a "Spectre Revelation Gadget", such straight-line speculation could lead to changes in the caches and similar structures that are indicative of secrets, making those secrets vulnerable to revelation through timing analysis. The gist of the mitigation is that for RET and BR instructions, a speculation barrier is placed af...