There were a fair amount of changes to workaround a firmware bug leaving
a pending interrupt after migration of the ibmvnic device :
commit 2df5c60e198c ("net/ibmvnic: Ignore H_FUNCTION return from H_EOI
to tolerate XIVE mode")
commit 284f87d2f387 ("Revert "net/ibmvnic: Fix EOI
From: Masahiro Yamada
> Sent: 17 February 2022 17:27
>
> On Fri, Feb 18, 2022 at 1:49 AM David Laight wrote:
> >
> > From: Masahiro Yamada
> > > Sent: 17 February 2022 16:17
> > ...
> > > No. Not that one.
> > >
> > > The commit you presumably want to revert is:
> > >
> > > a771f2b82aa2 ("[PATCH
On Wed, Feb 16, 2022 at 2:17 PM Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> Nine architectures are still missing __{get,put}_kernel_nofault:
> alpha, ia64, microblaze, nds32, nios2, openrisc, sh, sparc32, xtensa.
>
> Add a generic version that lets everything use the normal
> copy_{from,to}_ke
Hi Arnd,
On Wed, Feb 16, 2022 at 2:17 PM Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> While most m68k platforms use separate address spaces for user
> and kernel space, at least coldfire does not, and the other
> ones have a TASK_SIZE that is less than the entire 4GB address
> range.
>
> Using
On Wed, Feb 16, 2022 at 2:17 PM Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> There are many different ways that access_ok() is defined across
> architectures, but in the end, they all just compare against the
> user_addr_max() value or they accept anything.
>
> Provide one definition that works
n Fri, Feb 18, 2022 at 3:21 AM Al Viro wrote:
>
> On Thu, Feb 17, 2022 at 08:49:59AM +0100, Arnd Bergmann wrote:
>
> > Same here: architectures can already provide a __put_user_fn()
> > and __get_user_fn(), to get the generic versions of the interface,
> > but few architectures use that. You can a
On Fri, Feb 18, 2022 at 10:00 AM Geert Uytterhoeven
wrote:
> > /* We let the MMU do all checking */
> > -static inline int access_ok(const void __user *addr,
> > +static inline int access_ok(const void __user *ptr,
> > unsigned long size)
> > {
> > + unsigned lo
From: Andy Lutomirski
> Sent: 17 February 2022 19:15
...
> This isn't actually optimal. On x86, TASK_SIZE_MAX is a bizarre
> constant that has a very specific value to work around a bug^Wdesign
> error^Wfeature of Intel CPUs. TASK_SIZE_MAX is the maximum address at
> which userspace is permitted
Le 18/02/2022 à 02:50, Al Viro a écrit :
> On Thu, Feb 17, 2022 at 07:20:11AM +, Christophe Leroy wrote:
>
>> And we have also
>> user_access_begin()/user_read_access_begin()/user_write_access_begin()
>> which call access_ok() then do the real work. Could be made generic with
>> call to some
I think you could apply them as is, only criticism was the commit msgs.
Jocke
From: Thorsten Leemhuis
Sent: 18 February 2022 08:11
To: Leo Li; Joakim Tjernlund; eugene_bordenkirc...@selinc.com;
linux-...@vger.kernel.org; linuxppc-dev@lists.ozlabs.org
Cc
On Fri, Feb 18, 2022 at 10:21:12AM +, Joakim Tjernlund wrote:
> I think you could apply them as is, only criticism was the commit msgs.
That is always a good reason to reject a change. Please resubmit them
with the commit message cleaned up and I will be glad to review it
again.
thanks,
gre
Hi Palmer,
Do you intend to pull that in for-next or not yet? Can I do something to help?
Thanks,
Alex
On Mon, Jan 10, 2022 at 9:05 AM Alexandre ghiti wrote:
>
> Hi Palmer,
>
> Do you think this could go in for-next?
>
> Thanks,
>
> Alex
>
> On 12/6/21 10:44, Alexandre ghiti wrote:
> > @Palmer
I was happy with commit msgs and I don't know what the criticism was.
From: gre...@linuxfoundation.org
Sent: 18 February 2022 11:39
To: Joakim Tjernlund
Cc: Thorsten Leemhuis; Leo Li; eugene_bordenkirc...@selinc.com;
linux-...@vger.kernel.org; linuxppc-de
On Fri, Feb 18, 2022 at 11:17:59AM +, Joakim Tjernlund wrote:
> I was happy with commit msgs and I don't know what the criticism was.
I have no context anymore, sorry.
Can someone resubmit the change again and we can take it from there?
thanks,
greg k-h
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller :
On Fri, 18 Feb 2022 09:07:08 +0100 you wrote:
> There were a fair amount of changes to workaround a firmware bug leaving
> a pending interrupt after migration of the ibmvnic device :
>
> commit 2df5c60e198c ("net/
On Fri, Feb 18, 2022 at 10:35:48AM +0900, Masahiro Yamada wrote:
> On Fri, Feb 18, 2022 at 3:10 AM Segher Boessenkool
> wrote:
> > On Fri, Feb 18, 2022 at 02:27:16AM +0900, Masahiro Yamada wrote:
> > > On Fri, Feb 18, 2022 at 1:49 AM David Laight
> > > wrote:
> > > > That description is largely
From: Christoph Hellwig
> Sent: 18 February 2022 06:29
...
>
> > diff --git a/arch/x86/kernel/stacktrace.c b/arch/x86/kernel/stacktrace.c
> > index 15b058eefc4e..ee117fcf46ed 100644
> > --- a/arch/x86/kernel/stacktrace.c
> > +++ b/arch/x86/kernel/stacktrace.c
> > @@ -90,7 +90,7 @@ copy_stack_frame
On Fri, 18 Feb 2022 06:12:37 -0600
Segher Boessenkool wrote:
> On Fri, Feb 18, 2022 at 10:35:48AM +0900, Masahiro Yamada wrote:
> > On Fri, Feb 18, 2022 at 3:10 AM Segher Boessenkool
> > wrote:
> > > On Fri, Feb 18, 2022 at 02:27:16AM +0900, Masahiro Yamada wrote:
> > > > On Fri, Feb 18, 202
On Fri, Feb 18, 2022 at 08:29:20AM -0800, Stephen Hemminger wrote:
> On Fri, 18 Feb 2022 06:12:37 -0600
> Segher Boessenkool wrote:
> > On Fri, Feb 18, 2022 at 10:35:48AM +0900, Masahiro Yamada wrote:
> > > On Fri, Feb 18, 2022 at 3:10 AM Segher Boessenkool
> > > wrote:
> > > > On Fri, Feb 18,
The pull request you sent on Fri, 18 Feb 2022 13:54:05 +1100:
> https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
> tags/powerpc-5.17-4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ea4b3d299fe6b6c9afa4a91dc2cf5479d0089eeb
Thank you!
--
Deet-doot-d
On Thu, Feb 17, 2022 at 8:34 AM Kajol Jain wrote:
>
> Patchset adds performance stats reporting support for nvdimm.
> Added interface includes support for pmu register/unregister
> functions. A structure is added called nvdimm_pmu to be used for
> adding arch/platform specific data such as cpumask
On Fri, Feb 18, 2022 at 1:30 AM David Laight wrote:
>
> From: Andy Lutomirski
> > Sent: 17 February 2022 19:15
> ...
> > This isn't actually optimal. On x86, TASK_SIZE_MAX is a bizarre
> > constant that has a very specific value to work around a bug^Wdesign
> > error^Wfeature of Intel CPUs. TASK
Hello!
I was running a powerpc 32bit kernel (built using
qemu_ppc_mpc8544ds_defconfig
buildroot config, with enabling DEBUGFS+KMEMLEAK+HIGHMEM in the kernel
config)
on qemu and invoked the kmemleak scan (twice. for some reason the first
time wasn't enough).
(Actually the problem will probabl
https://bugzilla.kernel.org/show_bug.cgi?id=215621
Bug ID: 215621
Summary: Warning: Unable to mark rodata read only on this CPU.
(PPC970MP)
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.17-rc4
Hardw
https://bugzilla.kernel.org/show_bug.cgi?id=215621
--- Comment #1 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 300483
--> https://bugzilla.kernel.org/attachment.cgi?id=300483&action=edit
kernel .config (5.17-rc4, PowerMac G5 11,2)
--
You may reply to this email to add a comment
https://bugzilla.kernel.org/show_bug.cgi?id=215622
Bug ID: 215622
Summary: WARNING: possible irq lock inversion dependency
detected
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.17-rc4
Hardware: PPC
https://bugzilla.kernel.org/show_bug.cgi?id=215622
--- Comment #1 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 300485
--> https://bugzilla.kernel.org/attachment.cgi?id=300485&action=edit
kernel .config (5.17-rc4, PowerMac G5 11,2)
--
You may reply to this email to add a comment
On Fri, Feb 18, 2022 at 06:41:52PM +, Melanie Plageman (Microsoft) wrote:
> Currently a single blk_mq_tag_set is associated with a Scsi_Host. When SCSI
> controllers are limited, attaching multiple devices to the same controller is
> required. In cloud environments with relatively high latency
28 matches
Mail list logo
