linux-kernel - Re: [PATCH] vduse: make vduse

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] [day] [month] [year] [list]

Message-ID: <20231008030727-mutt-send-email-mst@kernel.org>
Date:   Sun, 8 Oct 2023 03:07:35 -0400
From:   "Michael S. Tsirkin" <mst@...hat.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     virtualization@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org, Jason Wang <jasowang@...hat.com>,
        Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
        Xie Yongji <xieyongji@...edance.com>
Subject: Re: [PATCH] vduse: make vduse_class constant

On Sun, Oct 08, 2023 at 08:46:45AM +0200, Greg Kroah-Hartman wrote:
> On Sun, Oct 08, 2023 at 02:41:22AM -0400, Michael S. Tsirkin wrote:
> > On Sun, Oct 08, 2023 at 08:40:05AM +0200, Greg Kroah-Hartman wrote:
> > > On Sun, Oct 08, 2023 at 02:20:52AM -0400, Michael S. Tsirkin wrote:
> > > > On Fri, Oct 06, 2023 at 04:30:44PM +0200, Greg Kroah-Hartman wrote:
> > > > > Now that the driver core allows for struct class to be in read-only
> > > > > memory, we should make all 'class' structures declared at build time
> > > > > placing them into read-only memory, instead of having to be dynamically
> > > > > allocated at runtime.
> > > > > 
> > > > > Cc: "Michael S. Tsirkin" <mst@...hat.com>
> > > > > Cc: Jason Wang <jasowang@...hat.com>
> > > > > Cc: Xuan Zhuo <xuanzhuo@...ux.alibaba.com>
> > > > > Cc: Xie Yongji <xieyongji@...edance.com>
> > > > > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > > > 
> > > > Acked-by: Michael S. Tsirkin <mst@...hat.com>
> > > > 
> > > > Greg should I merge it or do you intend to merge all these patches?
> > > 
> > > "all"?  There's loads of them for all sorts of subsystems, so feel free
> > > to take it through your subsystem tree if you want.  I usually scoop up
> > > the ones that no one picks after a release and take them through my
> > > tree, to pick up the stragglers.
> > > 
> > > So it's your call, whatever is easier for you is fine for me.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > To clarify which commit does this depend on?
> 
> The 6.4 kernel release :)

I'll pick this up then. Thanks!