lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 11 Sep 2012 15:13:53 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Paolo Bonzini <pbonzini@...hat.com>
Cc:	linux-kernel@...r.kernel.org, axboe@...nel.dk,
	linux-scsi@...r.kernel.org,
	"James E.J. Bottomley" <JBottomley@...allels.com>,
	Kay Sievers <kay.sievers@...y.org>,
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH] sg_io: allow UNMAP and WRITE SAME without CAP_SYS_RAWIO

Hello,

On Tue, Sep 11, 2012 at 3:10 PM, Paolo Bonzini <pbonzini@...hat.com> wrote:
> Il 12/09/2012 00:02, Tejun Heo ha scritto:
>> SG_IO itself is a bypassing interface.  It bypasses most of block
>> layer and the kernel doesn't have any idea (apart from the adhoc
>> filtering) about what's going on.
>
> That's very much the point.  The guest must have free reins.
>
> You asked "Could being able to bypass the filters for this "you own this
> LUN" be a solution?", I said yes and outlined how.  Do you agree with
> the proposed solution?

Ooh, yeah, I like that one. I was still thinking about the bpf one. It
being based on cgroup made me worried even more. :)

> Sure, I'm fine with leaving the current ad hoc filtering aside.  Again,
> I was hoping to get most of the job done by loosening the filter a bit,
> but discussion is inversely proportional to patch length sometimes.

Sorry about dragging it on. The cdb filtering one has always been
controversial and I think it'll continue to be. It's an unfortunate
thing that we had to add.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ